[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] | 6 | concept of <emphasis>runlevels</emphasis>. It can be widely different
|
---|
[53b5ccf] | 7 | from one system to another, so it can not be assumed that because things
|
---|
[0ad6d9a] | 8 | worked in <insert distro name> they should work like that in LFS
|
---|
| 9 | too. LFS has it's own way of doing things, but it respects generally
|
---|
[b822811] | 10 | accepted standards.</para>
|
---|
[0ad6d9a] | 11 |
|
---|
[b822811] | 12 | <para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works
|
---|
[a4d9786b] | 13 | using 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] | 15 | generally not used. The init man page describes those details), and each
|
---|
| 16 | one of those corresponds to the things the computer is supposed to do when
|
---|
[a4d9786b] | 17 | it starts up. The default runlevel is 3. Here are the descriptions of the
|
---|
[b822811] | 18 | different runlevels as they are often implemented:</para>
|
---|
[0ad6d9a] | 19 |
|
---|
[b822811] | 20 | <literallayout>0: halt the computer
|
---|
[0ad6d9a] | 21 | 1: single-user mode
|
---|
| 22 | 2: multi-user mode without networking
|
---|
| 23 | 3: multi-user mode with networking
|
---|
| 24 | 4: reserved for customization, otherwise does the same as 3
|
---|
[3ccc1df] | 25 | 5: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
|
---|
[b822811] | 26 | 6: reboot the computer</literallayout>
|
---|
[0ad6d9a] | 27 |
|
---|
[b822811] | 28 | <para>The command used to change runlevels is <userinput>init
|
---|
[443aab7] | 29 | <runlevel></userinput> where <runlevel> is
|
---|
[53b5ccf] | 30 | the target runlevel. For example, to reboot the computer, a user would issue
|
---|
[0ad6d9a] | 31 | the init 6 command. The reboot command is just an alias, as is the halt
|
---|
[b822811] | 32 | command 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] | 35 | before 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
|
---|
[78d46a5] | 39 | where ? is the number of the runlevel and rcS.d which contain a number of
|
---|
| 40 | symbolic links. Some begin with an K, the others begin with an S, and all
|
---|
[fa914e5] | 41 | of them have three numbers following the initial letter. The K means to
|
---|
| 42 | stop (kill) a service, and the S means to start a service. The numbers
|
---|
| 43 | determine the order in which the scripts are run, from 000 to 999; the
|
---|
| 44 | lower the number the sooner it gets executed. When init switches to
|
---|
| 45 | another runlevel, the appropriate services get killed and others get
|
---|
| 46 | started.</para>
|
---|
[0ad6d9a] | 47 |
|
---|
[b822811] | 48 | <para>The real scripts are in /etc/init.d. They do all the work, and the
|
---|
[fa914e5] | 49 | symlinks all point to them. Killing links and starting links point to
|
---|
| 50 | the same script in /etc/init.d. That's because the scripts can be
|
---|
| 51 | called with different parameters like start, stop, restart, reload,
|
---|
[0ad6d9a] | 52 | status. When a K link is encountered, the appropriate script is run with
|
---|
| 53 | the stop argument. When a S link is encountered, the appropriate script
|
---|
[b822811] | 54 | is run with the start argument.</para>
|
---|
[0ad6d9a] | 55 |
|
---|
[fa914e5] | 56 | <para>There is one exception. Links that start with an S in the
|
---|
| 57 | rc0.d and rc6.d directories will not cause anything to be started. They
|
---|
[090a0cc] | 58 | will be called with the parameter <emphasis>stop</emphasis> to stop
|
---|
[fa914e5] | 59 | something. The logic behind it is that when you are going to reboot or
|
---|
| 60 | halt the system, you don't want to start anything, only stop the
|
---|
| 61 | system.</para>
|
---|
| 62 |
|
---|
[b822811] | 63 | <para>These are descriptions of what the arguments make the
|
---|
| 64 | scripts do:</para>
|
---|
[b2c0c79] | 65 |
|
---|
| 66 | <itemizedlist>
|
---|
| 67 |
|
---|
[b822811] | 68 | <listitem><para><emphasis>start</emphasis>: The service is
|
---|
| 69 | started.</para></listitem>
|
---|
[b2c0c79] | 70 |
|
---|
[b822811] | 71 | <listitem><para><emphasis>stop</emphasis>: The service is
|
---|
| 72 | stopped.</para></listitem>
|
---|
[b2c0c79] | 73 |
|
---|
[b822811] | 74 | <listitem><para><emphasis>restart</emphasis>: The service is
|
---|
| 75 | stopped and then started again.</para></listitem>
|
---|
[b2c0c79] | 76 |
|
---|
[b822811] | 77 | <listitem><para><emphasis>reload</emphasis>: The configuration
|
---|
| 78 | of the service is updated.
|
---|
[53b5ccf] | 79 | This is used after the configuration file of a service was modified, when
|
---|
[b822811] | 80 | the service doesn't need to be restarted.</para></listitem>
|
---|
[b2c0c79] | 81 |
|
---|
[b822811] | 82 | <listitem><para><emphasis>status</emphasis>: Tells if the service
|
---|
| 83 | is 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] | 88 | LFS system, not ours). The files here are just an example of how it can be
|
---|
[b822811] | 89 | done in a nice way (well what we consider nice anyway. You may hate it).</para>
|
---|
[0ad6d9a] | 90 |
|
---|
| 91 | </sect1>
|
---|
| 92 |
|
---|