source: chapter07/usage.xml@ 68d17e8b

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.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_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/loongarch-12.2 xry111/mips64el xry111/multilib xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 68d17e8b was e12115e, checked in by Gerard Beekmans <gerard@…>, 23 years ago

added <?dbhtml> tag for output redirection into subdir

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

  • Property mode set to 100644
File size: 4.1 KB
RevLine 
[0ad6d9a]1<sect1 id="ch07-usage">
2<title>How does the booting process with these scripts work?</title>
[e12115e]3<?dbhtml filename="usage.html" dir="chapter07"?>
[0ad6d9a]4
[b822811]5<para>Linux uses a special booting facility named SysVinit. It's based on a
[0ad6d9a]6concept of <emphasis>runlevels</emphasis>. It can be widely different
[53b5ccf]7from one system to another, so it can not be assumed that because things
[0ad6d9a]8worked in &lt;insert distro name&gt; they should work like that in LFS
9too. LFS has it's own way of doing things, but it respects generally
[b822811]10accepted standards.</para>
[0ad6d9a]11
[b822811]12<para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works
[a4d9786b]13using a runlevels scheme. There are 7 (from 0 to 6) runlevels
14(actually, there are more runlevels but they are for special cases and
[53b5ccf]15generally not used. The init man page describes those details), and each
16one of those corresponds to the things the computer is supposed to do when
[a4d9786b]17it starts up. The default runlevel is 3. Here are the descriptions of the
[b822811]18different runlevels as they are often implemented:</para>
[0ad6d9a]19
[b822811]20<literallayout>0: halt the computer
[0ad6d9a]211: single-user mode
222: multi-user mode without networking
233: multi-user mode with networking
244: reserved for customization, otherwise does the same as 3
[3ccc1df]255: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
[b822811]266: reboot the computer</literallayout>
[0ad6d9a]27
[b822811]28<para>The command used to change runlevels is <userinput>init
[443aab7]29&lt;runlevel&gt;</userinput> where &lt;runlevel&gt; is
[53b5ccf]30the target runlevel. For example, to reboot the computer, a user would issue
[0ad6d9a]31the init 6 command. The reboot command is just an alias, as is the halt
[b822811]32command an alias to init 0.</para>
[0ad6d9a]33
[b822811]34<para>The /etc/init.d/rcS script is run at every startup of the computer,
[0ad6d9a]35before any runlevel is executed and runs the scripts listed in
[b822811]36/etc/rcS.d</para>
[0ad6d9a]37
[b822811]38<para>There are a number of directories under /etc that look like like rc?.d
[fa914e5]39where ? is the number of the runlevel and rcS.d which contain a number of s
40ymbolic links. Some begin with an K, the others begin with an S, and all
41of them have three numbers following the initial letter. The K means to
42stop (kill) a service, and the S means to start a service. The numbers
43determine the order in which the scripts are run, from 000 to 999; the
44lower the number the sooner it gets executed. When init switches to
45another runlevel, the appropriate services get killed and others get
46started.</para>
[0ad6d9a]47
[b822811]48<para>The real scripts are in /etc/init.d. They do all the work, and the
[fa914e5]49symlinks all point to them. Killing links and starting links point to
50the same script in /etc/init.d. That's because the scripts can be
51called with different parameters like start, stop, restart, reload,
[0ad6d9a]52status. When a K link is encountered, the appropriate script is run with
53the stop argument. When a S link is encountered, the appropriate script
[b822811]54is run with the start argument.</para>
[0ad6d9a]55
[fa914e5]56<para>There is one exception. Links that start with an S in the
57rc0.d and rc6.d directories will not cause anything to be started. They
[090a0cc]58will be called with the parameter <emphasis>stop</emphasis> to stop
[fa914e5]59something. The logic behind it is that when you are going to reboot or
60halt the system, you don't want to start anything, only stop the
61system.</para>
62
[b822811]63<para>These are descriptions of what the arguments make the
64scripts do:</para>
[b2c0c79]65
66<itemizedlist>
67
[b822811]68<listitem><para><emphasis>start</emphasis>: The service is
69started.</para></listitem>
[b2c0c79]70
[b822811]71<listitem><para><emphasis>stop</emphasis>: The service is
72stopped.</para></listitem>
[b2c0c79]73
[b822811]74<listitem><para><emphasis>restart</emphasis>: The service is
75stopped and then started again.</para></listitem>
[b2c0c79]76
[b822811]77<listitem><para><emphasis>reload</emphasis>: The configuration
78of the service is updated.
[53b5ccf]79This is used after the configuration file of a service was modified, when
[b822811]80the service doesn't need to be restarted.</para></listitem>
[b2c0c79]81
[b822811]82<listitem><para><emphasis>status</emphasis>: Tells if the service
83is running and with which PID's.</para></listitem>
[b2c0c79]84
85</itemizedlist>
[0ad6d9a]86
[b822811]87<para>Feel free to modify the way the boot process works (after all it's your
[53b5ccf]88LFS system, not ours). The files here are just an example of how it can be
[b822811]89done in a nice way (well what we consider nice anyway. You may hate it).</para>
[0ad6d9a]90
91</sect1>
92
Note: See TracBrowser for help on using the repository browser.