Firewalld
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So, I was working on some firewalld rules today, and encountered
situations we haven't documented, as well as some new features we
haven't covered. It got me thinking about the way we document
firewalls; some things in the Security Guide, some allusions in the
Networking Guide or Sysadmin Guide, some missing. I think that a
general overview of firewalld and basic usage is appropriate in all of
these places, but I don't like the omission when a book gets down to
specifics.
So, which Guide should provide indepth coverage of the firewall? Eric
and Stephen, fight!
Here's my idea: In the security guide, give an overview, instructions
on how to lock down to deny-all, general instructions on adding back,
and link out to the Networking Guide. In the NG, give a full overview -
network security should be an inherent part of network configuration.
In others, include the command to open a port for the service being
documented where appropriate.
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org we havent covered
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJT+4rqAAoJEL1wZM0+jj2ZAE4H/jxg3qdrZ08ioLM3W8T+Ubsn
Rvfaq5nawBLjtc/xvwX4awjtZRDLgfugoxQnDb4gog0W1/f1BrZ6+fs6qvAAxtKb
oIXE4QCegLsva1c4LfAPE/DCxqFiFWGK65jdXD3dytx/I+Y9xCEYpMR/huLwApiL
zN7hZ+OUgfNswLRowPcqCPmPFWFJOefnDB7wNPh/heChXZ2MM2lLKa41TabaPYfw
Rgi8/5RwJR+6BVs2aG72dgP9gIZ6EmPIanKr95/4Tpd6xsBYwgL1wvPqIAn+KXUe
INwpXLu1iVIL3s99R1kZdIdoPP2wHOv2y31YabuAKUEVr9MIizLjIsGQ+k1OXFM=
=8Zi9
-----END PGP SIGNATURE-----
9 years, 7 months
Fedora Docs Meeting Minutes 25 Aug 2014
by Pete Travis
Things got a little strange after I changed IRC handles during the
meeting - for best results, you'll want to review the full logs.
============================
#fedora-meeting: Fedora Docs
============================
Meeting started by radnomuser` at 14:05:57 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-08-25/fedora_docs.20...
.
Meeting summary
---------------
* LINK:
https://fedoraproject.org/wiki/Docs_Project_meetings#Standing_Agenda
(randomuser, 14:07:50)
* LINK:
https://fedorapeople.org/groups/schedule/f-21/f-21-docs-tree-tasks.html
(randomuser, 14:22:06)
* LINK: http://red.ht/1sPgI5t (pbokoc, 14:29:50)
* ACTION: pbokoc to add bz query links to Category:Beats page
(randomuser, 14:33:55)
* ACTION: randomuser to QA FranciscoD's taskd recipe (randomuser,
14:54:05)
* sunspots (randomuser, 14:58:51)
Meeting ended at 15:02:08 UTC.
Action Items
------------
* pbokoc to add bz query links to Category:Beats page
* randomuser to QA FranciscoD's taskd recipe
Action Items, by person
-----------------------
* FranciscoD
* randomuser to QA FranciscoD's taskd recipe
* pbokoc
* pbokoc to add bz query links to Category:Beats page
* randomuser
* randomuser to QA FranciscoD's taskd recipe
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* randomuser (75)
* pbokoc (55)
* lnovich (20)
* jhunt|mtg (7)
* jreznik (7)
* pkovar (6)
* adamw (4)
* yruseva (4)
* zodbot (4)
* Capesteve (4)
* handsome_pirate (3)
* rkratky (2)
* radnomuser` (2)
* FranciscoD (1)
* bara_ (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
9 years, 7 months
New member
by Eric Griffith
Greetings all,
I have used Fedora for a number of years now (a few of you may have
seen me in the forums, or on Phoronix), but I have decided that I wish
to finally contribute to the project itself. As I just starting to
learn Python, C++, and HTML/CSS/JS, but I am starting school for a
Bachelor's Of English, I thought documentation would be the best way
to start and get my foot in the door.
I am also requesting permission to join the "docs" group on FAS for my
user (egriffith), as well as a pointing-in-the-right-direction for
where to get started contributing.
Cheers,
--Ericg--
9 years, 7 months
documentation for translation
by Noriko Mizumoto
Hi docs team and websites team
As many of you already notice, translation team is planning to move from
Transifex to Zanata. The detailed info is available this page [1].
>From F22, we are looking at to accept translation at newly created
instance. Please notice that nothing is changed or impacted for F21.
Now I am gathering the information of all involved package owners, so
that I can send out necessary information for the move to each owner
timely manner. Could you kindly check the sheet '2nd-docs' or
'3rd-websites' in the spreadsheet [2] and advise if any deprecated
document, if any owner update, if any new document to add, etc?
Also we are going to set up adequate time frame to move for owners. Atm,
the plan is that 'upstream' and/or 'docs' start to move, and followed by
'websites' and 'main', rough estimation is one month.
How many weeks do your teams need to move? When the best timing for your
teams?
[1]:https://fedoraproject.org/wiki/L10N_Move_To_Zanata
[2]:https://docs.google.com/a/griffithuni.edu.au/spreadsheets/d/1EFvaz8Fd7...
Thanks in advance
noriko
Fedora Localization Project
9 years, 7 months
Self-Introduction
by Jacob Hunt
Hello,
I'm new to the list and would like to participate in Fedora Documentation Project, and I'm requesting access to the "docs" group on FAS for my account (jhunt).
I work at Red Hat as a Sr. Technical Account Manager (TAM) and have been here for several years, initially starting as a Consultant and RHCE Instructor at Red Hat. As part of my role I have to create and maintain custom documentation for my accounts. I use LyX [1] to create all my documentation I like the professional look it gives my documents plus all the nice features compared to the common word processors. I've dabbled with Publican a bit, but have no problem learning how to effectively use it to create documentation.
I live outside of Boise, ID, US (UTC -6) and work from home as a remote employee. Unless there is a need elsewhere I was thinking of helping on the Category Pages [2] to start.
Thank you,
Jacob Hunt, RHCE
Sr. Technical Account Manager
Global Support Services
Red Hat, Inc.
mobile (208) 794-3408
office (650) 254-4263
Key ID = DB7CBBE7
Key fingerprint = 163D 55B2 4C85 0C0B C4FA 9C2A C860 E3B1 DB7C BBE7
[1] http://www.lyx.org
[2] https://fedoraproject.org/wiki/Category:Pages_that_need_love
9 years, 8 months
zRAM Swap Support in Anaconda
by Leslie S Satenstein
Hello from Montreal Quebec, Canada
I have some comments about the Installer document ( http://fedoraproject.org/wiki/Documentation_Beats_Installer ). It is mainly about grammar and sentences. I have been a tech writer as a profession and also a system architect. So my comments are inline below with either italics or in red font or as a Revison.Text to be removed is in bold Italics and in a smaller font
Original TEXT Revised follows.
zRAM Swap Support in Anaconda
The Anaconda installer now supports swap on zRAM during the installation.
zRAM is a standard block device with its contents compressed.
Placing swap into such device during the installation allows the
installer to store more data in RAM instead of the hard drive. This is
especially helpful on systems with low amounts of RAM available -
installation on these systems now runs significantly faster. Testing
also shows that with zRAM swap, it is now possible to install Fedora on
systems with as little as 320 MB RAM.
This feature is automatically enabled if Anaconda detects 2 GB or less memory, and disabled on systems with more than 2 GB RAM. This
behavior can be changed by using the inst.zram=on or inst.zram=off boot option at the boot menu to force zRAM swap on or off.
Specific limits, numbers and way of implementation may be changed in the future.
Changes in Anaconda Boot Options
A boot option is an option used to modify the installer's behavior on the boot command line. The following boot options have been added in
Fedora 21:
* inst.zram= - use this option to force zRAM swap on (inst.zram=on) or off (inst.zram=off).
* inst.dnf - forces Anaconda to use the experimental DNF backend for package installation instead of YUM
* inst.memcheck - perform a check at the beginning
of the installation to see if there is enough available RAM, and stop
the installation with an error message if there is not. This option is
enabled by default, however, you can use inst.memcheck=0 to it.
REVISED
zRAM is a standard block device with its contents stored in compressed format. The Anaconda installer now supports swap using zRAM during the installation.
Placing swap into such device during the installation allows the
installer to store more data in RAM instead of in the hard drive. This is
especially helpful on systems with low amounts of available RAM available - Fedora
installationon these zRAM systems now runs significantly faster. Testing also shows that with installations using zRAM swap, it is now possible to install Fedora on systems with as little as 320 MB RAM.
(Remove "with" and "now" ),
This feature is automatically enabled if Anaconda detects 2 GB or
less memory, and disabled on systems with more than 2 GB RAM. This
behavior can be changed by using the inst.zram=on or inst.zram=off
Changes in Anaconda Boot Options
A boot option is an option used to modify the installer's behavior on the boot command line. The following boot options have been added in
Fedora 21:
* inst.zram= - use this option to activate zRAM swap on ( (remove the "on" ) inst.zram=on) or off (inst.zram=off).
* inst.dnf - forces Anaconda to use the experimental DNF backend for package installation instead of YUM
* inst.memcheck - perform a check at the beginning
of the installation to see if there is enough available RAM, and otherwise stop
the installation with an error message if there is not. This option is
enabled by default, however, you can use inst.memcheck=0 to disable it.
END OF REVISION
My personal comment.
For two years I have been offering to correct and verify the English text, prior to it's going to translators. Somehow that has never been acted upon. Please note, technical writing must be ego-less. Many times, when I was writing professionally, I thought I had a great document, only to have the editor come back to me with big Xs on the pages. I had to learn to accept the editor's feedback after negotiation.
I would very much prefer to use a proper word processor to complete the edits. Libreoffice has a text markup facility, and it would be faster and easier to make use of it, rather than the po type of writing support for first and second drafts.
If I am out of line, I apologize, but Fedora documentation must be as good as the Fedora release, and we often know that good programmers are less skilled at documentation writing.
Regards
Leslie
Mr. Leslie Satenstein
Fedora User since Fedora core.
9 years, 8 months
