[install-guide: 11/18] purging out legacy init scripts info

Pete Travis immanetize at fedoraproject.org
Fri Oct 26 05:51:48 UTC 2012


commit be8359e36e1e71388d297b632e93e420f770a6bd
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Tue Sep 11 00:32:13 2012 -0600

    purging out legacy init scripts info

 en-US/Boot_Init_Shutdown.xml |  104 +-----------------------------------------
 1 files changed, 1 insertions(+), 103 deletions(-)
---
diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
index f404b1b..ad4c01f 100644
--- a/en-US/Boot_Init_Shutdown.xml
+++ b/en-US/Boot_Init_Shutdown.xml
@@ -376,109 +376,7 @@ Let's look at the different types of units:
 			 <para>
 			   The function and usage of legacy init systems and their configuration files is outside of the scope of this document.
 			</para>
-			 <para>
-				Next, the <command>init</command> command sets the source function library, <filename>/etc/rc.d/init.d/functions</filename>, for the system, which configures how to start, kill, and determine the PID of a program.
-			</para>
-			 <para>
-				The <command>init</command> program starts all of the background processes by looking in the appropriate <filename>rc</filename> directory for the runlevel specified as the default in <filename>/etc/inittab</filename>. The <filename>rc</filename> directories are numbered to correspond to the runlevel they represent. For instance, <filename>/etc/rc.d/rc5.d/</filename> is the directory for runlevel 5.
-			</para>
-			 <para>
-				When booting to runlevel 5, the <command>init</command> program looks in the <filename>/etc/rc.d/rc5.d/</filename> directory to determine which processes to start and stop.
-			</para>
-			 <para>
-				Below is an example listing of the <filename>/etc/rc.d/rc5.d/</filename> directory:
-			</para>
-			
-<screen>
-K05innd -&gt; ../init.d/innd 
-K05saslauthd -&gt; ../init.d/saslauthd 
-K10dc_server -&gt; ../init.d/dc_server 
-K10psacct -&gt; ../init.d/psacct 
-K10radiusd -&gt; ../init.d/radiusd 
-K12dc_client -&gt; ../init.d/dc_client 
-K12FreeWnn -&gt; ../init.d/FreeWnn 
-K12mailman -&gt; ../init.d/mailman 
-K12mysqld -&gt; ../init.d/mysqld 
-K15httpd -&gt; ../init.d/httpd 
-K20netdump-server -&gt; ../init.d/netdump-server 
-K20rstatd -&gt; ../init.d/rstatd 
-K20rusersd -&gt; ../init.d/rusersd 
-K20rwhod -&gt; ../init.d/rwhod 
-K24irda -&gt; ../init.d/irda 
-K25squid -&gt; ../init.d/squid 
-K28amd -&gt; ../init.d/amd 
-K30spamassassin -&gt; ../init.d/spamassassin 
-K34dhcrelay -&gt; ../init.d/dhcrelay 
-K34yppasswdd -&gt; ../init.d/yppasswdd 
-K35dhcpd -&gt; ../init.d/dhcpd 
-K35smb -&gt; ../init.d/smb 
-K35vncserver -&gt; ../init.d/vncserver 
-K36lisa -&gt; ../init.d/lisa 
-K45arpwatch -&gt; ../init.d/arpwatch 
-K45named -&gt; ../init.d/named 
-K46radvd -&gt; ../init.d/radvd 
-K50netdump -&gt; ../init.d/netdump 
-K50snmpd -&gt; ../init.d/snmpd 
-K50snmptrapd -&gt; ../init.d/snmptrapd 
-K50tux -&gt; ../init.d/tux 
-K50vsftpd -&gt; ../init.d/vsftpd 
-K54dovecot -&gt; ../init.d/dovecot 
-K61ldap -&gt; ../init.d/ldap 
-K65kadmin -&gt; ../init.d/kadmin 
-K65kprop -&gt; ../init.d/kprop 
-K65krb524 -&gt; ../init.d/krb524 
-K65krb5kdc -&gt; ../init.d/krb5kdc 
-K70aep1000 -&gt; ../init.d/aep1000 
-K70bcm5820 -&gt; ../init.d/bcm5820 
-K74ypserv -&gt; ../init.d/ypserv 
-K74ypxfrd -&gt; ../init.d/ypxfrd 
-K85mdmpd -&gt; ../init.d/mdmpd 
-K89netplugd -&gt; ../init.d/netplugd 
-K99microcode_ctl -&gt; ../init.d/microcode_ctl 
-S04readahead_early -&gt; ../init.d/readahead_early 
-S05kudzu -&gt; ../init.d/kudzu 
-S06cpuspeed -&gt; ../init.d/cpuspeed 
-S08ip6tables -&gt; ../init.d/ip6tables 
-S08iptables -&gt; ../init.d/iptables 
-S09isdn -&gt; ../init.d/isdn 
-S10network -&gt; ../init.d/network 
-S12syslog -&gt; ../init.d/syslog 
-S13irqbalance -&gt; ../init.d/irqbalance 
-S13portmap -&gt; ../init.d/portmap 
-S15mdmonitor -&gt; ../init.d/mdmonitor 
-S15zebra -&gt; ../init.d/zebra 
-S16bgpd -&gt; ../init.d/bgpd 
-S16ospf6d -&gt; ../init.d/ospf6d 
-S16ospfd -&gt; ../init.d/ospfd 
-S16ripd -&gt; ../init.d/ripd 
-S16ripngd -&gt; ../init.d/ripngd 
-S20random -&gt; ../init.d/random 
-S24pcmcia -&gt; ../init.d/pcmcia 
-S25netfs -&gt; ../init.d/netfs 
-S26apmd -&gt; ../init.d/apmd 
-S27ypbind -&gt; ../init.d/ypbind 
-S28autofs -&gt; ../init.d/autofs 
-S40smartd -&gt; ../init.d/smartd 
-S44acpid -&gt; ../init.d/acpid 
-S54hpoj -&gt; ../init.d/hpoj 
-S55cups -&gt; ../init.d/cups 
-S55sshd -&gt; ../init.d/sshd 
-S56rawdevices -&gt; ../init.d/rawdevices 
-S56xinetd -&gt; ../init.d/xinetd 
-S58ntpd -&gt; ../init.d/ntpd 
-S75postgresql -&gt; ../init.d/postgresql 
-S80sendmail -&gt; ../init.d/sendmail 
-S85gpm -&gt; ../init.d/gpm 
-S87iiim -&gt; ../init.d/iiim 
-S90canna -&gt; ../init.d/canna 
-S90crond -&gt; ../init.d/crond 
-S90xfs -&gt; ../init.d/xfs 
-S95atd -&gt; ../init.d/atd 
-S96readahead -&gt; ../init.d/readahead 
-S97messagebus -&gt; ../init.d/messagebus 
-S97rhnsd -&gt; ../init.d/rhnsd 
-S99local -&gt; ../rc.local
-</screen>
+			 
 			 <para>
 				As illustrated in this listing, none of the scripts that actually start and stop the services are located in the <filename>/etc/rc.d/rc5.d/</filename> directory. Rather, all of the files in <filename>/etc/rc.d/rc5.d/</filename> are <firstterm>symbolic links</firstterm> pointing to scripts located in the <filename>/etc/rc.d/init.d/</filename> directory. Symbolic links are used in each of the <filename>rc</filename> directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference.
 			</para>


More information about the docs-commits mailing list