Ignore:
Timestamp:
07/02/2005 05:56:57 AM (19 years ago)
Author:
Archaic <archaic@…>
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, 12.2, 12.2-rc1, 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, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
ffd471a
Parents:
440f837
Message:

Several minor wording changes in chapter 8 (matt).

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/usage.xml

    r440f837 rfaca37e  
    1212<secondary>usage</secondary></indexterm>
    1313
    14 <para>Linux uses a special booting facility named SysVinit that is
    15 based on a concept of <emphasis>run-levels</emphasis>. It can be quite
    16 different from one system to another, so it cannot be assumed that
    17 because things worked in &lt;insert distro name&gt;, they should work
    18 the same in LFS too. LFS has its own way of doing things, but it
    19 respects generally accepted standards.</para>
     14<para>Linux uses a special booting facility named SysVinit that is based on a
     15concept of <emphasis>run-levels</emphasis>. It can be quite different from one
     16system to another, so it cannot be assumed that because things worked in one
     17particular Linux distribution, they should work the same in LFS too. LFS has its
     18own way of doing things, but it respects generally accepted standards.</para>
    2019
    21 <para>SysVinit (which will be referred to as <quote>init</quote> from
    22 now on) works using a run-levels scheme. There are seven (from 0 to 6)
    23 run-levels (actually, there are more run-levels, but they are for
    24 special cases and are generally not used. The init man page describes
    25 those details), and each one of those corresponds to the actions the
    26 computer is supposed to perform when it starts up. The default
    27 run-level is 3. Here are the descriptions of the different run-levels
    28 as they are implemented:</para>
     20<para>SysVinit (which will be referred to as <quote>init</quote> from now on)
     21works using a run-levels scheme. There are seven (from 0 to 6) run-levels
     22(actually, there are more run-levels, but they are for special cases and are
     23generally not used. The init manual page describes those details), and each one
     24of those corresponds to the actions the computer is supposed to perform when it
     25starts up. The default run-level is 3. Here are the descriptions of the
     26different run-levels as they are implemented:</para>
    2927
    3028<literallayout>0: halt the computer
     
    3836<para>The command used to change run-levels is <command>init
    3937<replaceable>[runlevel]</replaceable></command>, where
    40 <replaceable>[runlevel]</replaceable> is the target run-level. For
    41 example, to reboot the computer, a user would issue the <command>init
    42 6</command> command.  The <command>reboot</command> command is an
    43 alias for it, as is the <command>halt</command> command an alias for
    44 <command>init 0</command>.</para>
     38<replaceable>[runlevel]</replaceable> is the target run-level. For example, to
     39reboot the computer, a user could issue the <command>init 6</command> command,
     40which is an alias for the <command>reboot</command> command. Likewise,
     41<command>init 0</command> is an alias for the <command>halt</command>
     42command.</para>
    4543
    4644<para>There are a number of directories under <filename
    4745class="directory">/etc/rc.d</filename> that look like <filename
    48 class="directory">rc?.d</filename> (where ? is the number of the
    49 run-level) and <filename class="directory">rcsysinit.d</filename>, all
    50 containing a number of symbolic links. Some begin with a
    51 <emphasis>K</emphasis>, the others begin with an
    52 <emphasis>S</emphasis>, and all of them have two numbers following the
    53 initial letter. The K means to stop (kill) a service and the S means
    54 to start a service. The numbers determine the order in which the
    55 scripts are run, from 00 to 99&mdash;the lower the number the earlier it
    56 gets executed. When init switches to another run-level, the
    57 appropriate services get killed and others get started.</para>
     46class="directory">rc?.d</filename> (where ? is the number of the run-level) and
     47<filename class="directory">rcsysinit.d</filename>, all containing a number of
     48symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
     49an <emphasis>S</emphasis>, and all of them have two numbers following the
     50initial letter. The K means to stop (kill) a service and the S means to start a
     51service. The numbers determine the order in which the scripts are run, from 00
     52to 99&mdash;the lower the number the earlier it gets executed. When
     53<command>init</command> switches to another run-level, the appropriate services
     54are either started or stopped, depending on the runlevel chosen.</para>
    5855
    5956<para>The real scripts are in <filename
Note: See TracChangeset for help on using the changeset viewer.