Ignore:
Timestamp:
07/22/2001 07:45:10 PM (23 years ago)
Author:
Mark Hymers <markh@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
f1da843
Parents:
46f5461
Message:

XML changes

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@827 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/usage.xml

    r46f5461 rb822811  
    22<title>How does the booting process with these scripts work?</title>
    33
    4 <para>
    5 Linux uses a special booting facility named SysVinit. It's based on a
     4<para>Linux uses a special booting facility named SysVinit. It's based on a
    65concept of <emphasis>runlevels</emphasis>. It can be widely different
    76from one system to another, so it can not be assumed that because things
    87worked in &lt;insert distro name&gt; they should work like that in LFS
    98too. LFS has it's own way of doing things, but it respects generally
    10 accepted standards.
    11 </para>
     9accepted standards.</para>
    1210
    13 <para>
    14 SysVinit (which we'll call <emphasis>init</emphasis> from now on) works
     11<para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works
    1512using a runlevels scheme. There are 7 (from 0 to 6) runlevels
    1613(actually, there are more runlevels but they are for special cases and
    … …  
    1815one of those corresponds to the things the computer is supposed to do when
    1916it starts up. The default runlevel is 3. Here are the descriptions of the
    20 different runlevels as they are often implemented:
    21 </para>
     17different runlevels as they are often implemented:</para>
    2218
    23 <literallayout>
    24 0: halt the computer
     19<literallayout>0: halt the computer
    25201: single-user mode
    26212: multi-user mode without networking
    … …  
    28234: reserved for customization, otherwise does the same as 3
    29245: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
    30 6: reboot the computer
    31 </literallayout>
     256: reboot the computer</literallayout>
    3226
    33 <para>
    34 The command used to change runlevels is <userinput>init
     27<para>The command used to change runlevels is <userinput>init
    3528&lt;runlevel&gt;</userinput> where &lt;runlevel&gt; is
    3629the target runlevel. For example, to reboot the computer, a user would issue
    3730the init 6 command. The reboot command is just an alias, as is the halt
    38 command an alias to init 0.
    39 </para>
     31command an alias to init 0.</para>
    4032
    41 <para>
    42 The /etc/init.d/rcS script is run at every startup of the computer,
     33<para>The /etc/init.d/rcS script is run at every startup of the computer,
    4334before any runlevel is executed and runs the scripts listed in
    44 /etc/rcS.d
    45 </para>
     35/etc/rcS.d</para>
    4636
    47 <para>
    48 There are a number of directories under /etc that look like like rc?.d
     37<para>There are a number of directories under /etc that look like like rc?.d
    4938where ? is the number of the runlevel and rcS.d. A user might take a look
    5039at one of
    … …  
    5645are run, from 000 to 999; the lower the number the sooner it gets
    5746executed. When init switches to another runlevel, the appropriate
    58 services get killed and others get started.
    59 </para>
     47services get killed and others get started.</para>
    6048
    61 <para>
    62 The real scripts are in /etc/init.d. They do all the work, and the
     49<para>The real scripts are in /etc/init.d. They do all the work, and the
    6350symlinks all point to them. Killing links and starting
    6451links point to the same script in /etc/init.d. That's because the scripts
    … …  
    6653status. When a K link is encountered, the appropriate script is run with
    6754the stop argument. When a S link is encountered, the appropriate script
    68 is run with the start argument.
    69 </para>
     55is run with the start argument.</para>
    7056
    71 <para>
    72 These are descriptions of what the arguments make the scripts do:
    73 </para>
     57<para>These are descriptions of what the arguments make the
     58scripts do:</para>
    7459
    7560<itemizedlist>
    7661
    77 <listitem><para>
    78 <emphasis>start</emphasis>: The service is started.
    79 </para></listitem>
     62<listitem><para><emphasis>start</emphasis>: The service is
     63started.</para></listitem>
    8064
    81 <listitem><para>
    82 <emphasis>stop</emphasis>: The service is stopped.
    83 </para></listitem>
     65<listitem><para><emphasis>stop</emphasis>: The service is
     66stopped.</para></listitem>
    8467
    85 <listitem><para>
    86 <emphasis>restart</emphasis>: The service is stopped and then started again.
    87 </para></listitem>
     68<listitem><para><emphasis>restart</emphasis>: The service is
     69stopped and then started again.</para></listitem>
    8870
    89 <listitem><para>
    90 <emphasis>reload</emphasis>: The configuration of the service is updated.
     71<listitem><para><emphasis>reload</emphasis>: The configuration
     72of the service is updated.
    9173This is used after the configuration file of a service was modified, when
    92 the service doesn't need to be restarted.
    93 </para></listitem>
     74the service doesn't need to be restarted.</para></listitem>
    9475
    95 <listitem><para>
    96 <emphasis>status</emphasis>: Tells if the service is running and with
    97 which PID's.
    98 </para></listitem>
     76<listitem><para><emphasis>status</emphasis>: Tells if the service
     77is running and with which PID's.</para></listitem>
    9978
    10079</itemizedlist>
    10180
    102 <para>
    103 Feel free to modify the way the boot process works (after all it's your
     81<para>Feel free to modify the way the boot process works (after all it's your
    10482LFS system, not ours). The files here are just an example of how it can be
    105 done in a nice way (well what we consider nice anyway. You may hate it).
    106 </para>
     83done in a nice way (well what we consider nice anyway. You may hate it).</para>
    10784
    10885</sect1>
Note: See TracChangeset for help on using the changeset viewer.