Changeset 7ebcd28

Timestamp:

03/21/2022 08:04:04 PM (2 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

53b26d6

Parents:

d54813b

Message:

Clarify SysV run levels.
Update the meaning of run level 2.

Add some clarifying remarks about run levels 0 and 6 (halt and reboot).

File:

• chapter09/usage.xml (modified) (3 diffs)

chapter09/usage.xml

@@ -36 +36 @@
 <literallayout>0: halt the computer
 1: single-user mode
-2: multi-user mode without networking
+2: reserved for customization, otherwise does the same as 3
 3: multi-user mode with networking
 4: reserved for customization, otherwise does the same as 3
 5: same as 4, it is usually used for GUI login (like X's <command>xdm</command> or KDE's <command>kdm</command>)
 6: reboot the computer</literallayout>
+
+    <note>
+       <para>
+          Classically, run level 2 above was defined as 
+          "multi-user mode without networking", but this was only the case 
+          many years ago when multiple users could log into a system connected via
+          serial ports.  In today's environment it makes no sense and
+          we designate it now as "reserved".
+       </para>
+    </note>
 
   </sect2>
@@ -128 +138 @@
   class="directory">/etc/rc.d</filename> that look like <filename
   class="directory">rc?.d</filename> (where ? is the number of the run-level) and
-  <filename class="directory">rcsysinit.d</filename>, all containing a number of
+  <filename class="directory">rcS.d</filename>, all containing a number of
   symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
   an <emphasis>S</emphasis>, and all of them have two numbers following the
@@ -156 +166 @@
   <parameter>stop</parameter> to stop something. The logic behind this
   is that when a user is going to reboot or halt the system, nothing
-  needs to be started.  The system only needs to be stopped.</para>
+  needs to be started, but the order of shutdown needs to be controlled.
+  For these run levels, all <emphasis>K</emphasis> prefixed scripts will be 
+  run before any <emphasis>S</emphasis> prefixed scripts are run with the
+  <parameter>stop</parameter> parameter.
+  </para>
 
   <para>These are descriptions of what the arguments make the scripts