Bug 756144 - Error in F16 System Administrator Guide
Summary: Error in F16 System Administrator Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: system-administrator's-guide
Version: devel
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jaromir Hradilek
QA Contact: Christopher Antila
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-22 19:57 UTC by Aaron Konstam
Modified: 2012-06-18 16:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-18 16:25:40 UTC
Embargoed:


Attachments (Terms of Use)
patch to systemd-administrators-guide.git (1.86 KB, patch)
2011-11-24 04:44 UTC, T.C. Hollingsworth
no flags Details | Diff

Description Aaron Konstam 2011-11-22 19:57:42 UTC
Description of problem:
Error in F16 System Administrator Guide

Version-Release number of selected component (if applicable):
Fedora 16

How reproducible:
Everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
In section E4 of the System Administrators Guide it says that the running of sysctl to set the kernel parameters is done by running the script 
/etc/rc.d/rc.sysinit.
Since this script does not exist in F16 I think this section should be corrected to say (at least I think this is the correct information) that systemd arranges to set the kernel parameters.

Comment 1 T.C. Hollingsworth 2011-11-24 04:44:33 UTC
Created attachment 535768 [details]
patch to systemd-administrators-guide.git

This patch updates the relevant section for systemd and also briefly explains the new /etc/sysctl.d behavior it adds.

Comment 2 Aaron Konstam 2011-12-22 12:33:11 UTC
The patch still has a problem. It refers to init running at boot. I think it would be useful to note that due to a link it is actually systemd that is running. For so long init had a different place in the boot process an emphasis would be useful that init as really been abandoned and it is systemd that has taken over the job of  process 1. This confusion is enforced by the fact that in the ps list init showa up as process 1.

Comment 3 T.C. Hollingsworth 2011-12-24 19:06:00 UTC
(In reply to comment #2)
> The patch still has a problem. It refers to init running at boot. I think it
> would be useful to note that due to a link it is actually systemd that is
> running. For so long init had a different place in the boot process an emphasis
> would be useful that init as really been abandoned and it is systemd that has
> taken over the job of  process 1

I don't think this is the right place to mention systemd's takeover of PID 1.  It really doesn't do anything different from upstart or init here.  The section of the guide that deals with starting, stopping, enabling, and disabling services does mention systemd in detail.

> This confusion is enforced by the fact that
> in the ps list init showa up as process 1.

The kernel is programmed to start /sbin/init.  It's a lot simpler to link that to systemd than patch the kernel or change the kernel command line.  ps shows the command line that started the program, but tools that show what's actually running (like ksysguard and probably GNOME's equivalent too) do say "systemd".  (There's probably a ps argument to do that too, but I don't know much beyond "ps aux" ;-)

Comment 4 Aaron Konstam 2011-12-25 14:33:27 UTC
I guess I don't agree with your comments. This is a System Administrator's Guide so I guess it for System Administrators. What better place to tell this audience just how the start of the system is carried out. 

I understand that init is used because of the kernel standard approach to start the processes get started, But that should be made clear to people who read this manual.

But it is not worth arguing about this.

Comment 5 T.C. Hollingsworth 2011-12-25 14:45:48 UTC
(In reply to comment #4)
> I guess I don't agree with your comments. This is a System Administrator's
> Guide so I guess it for System Administrators. What better place to tell this
> audience just how the start of the system is carried out. 

It does, in the "Services and Daemons" section:
http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/ch-Services_and_Daemons.html

I just think this is orthogonal to the sysctl issue, where systemd doesn't really make much of a difference.  If there's a problem there, it should be taken up in a new bug.

Comment 6 Jaromir Hradilek 2012-01-02 17:57:59 UTC
Fixed in:

  commit 8e855debd6eec1631fa84f5869b1323426074484
  commit d56ba626eecc8b486399350632a679f94d138ea0

Thank you very much for the patch and valuable comments. I have applied a slightly modified version of the patch and published an up-to-date draft version of the guide, so that you can verify that the text is accurate:

http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/System_Administrators_Guide/s1-proc-sysctl.html

As for the systemd documentation, I tend to agree with T.C. Hollingsworth on this: there is a more prominent place in the book to document the introduction of systemd in Fedora, and it is the Services and Daemons chapter. Feel free to add any comments to bug 707687, which serves as an RFE for such a documentation.

Comment 7 T.C. Hollingsworth 2012-01-02 19:55:45 UTC
(In reply to comment #6)
> Fixed in:
> 
>   commit 8e855debd6eec1631fa84f5869b1323426074484
>   commit d56ba626eecc8b486399350632a679f94d138ea0
> 
> Thank you very much for the patch and valuable comments. I have applied a
> slightly modified version of the patch and published an up-to-date draft
> version of the guide, so that you can verify that the text is accurate:
> 
> http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/System_Administrators_Guide/s1-proc-sysctl.html

Looks good!  Thanks a lot.

Comment 8 Christopher Antila 2012-01-16 04:56:09 UTC
Looks good to me too.

Comment 9 Jaromir Hradilek 2012-06-18 16:25:40 UTC
Thank you, guys.


Note You need to log in before you can comment on or make changes to this bug.