1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
---|
3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
4 | %general-entities;
|
---|
5 | ]>
|
---|
6 | <sect1 id="ch-scripts-usage">
|
---|
7 | <title>How does the booting process with these scripts work?</title>
|
---|
8 | <?dbhtml filename="usage.html"?>
|
---|
9 |
|
---|
10 | <indexterm zone="ch-scripts-usage">
|
---|
11 | <primary sortas="a-Bootscripts">Bootscripts</primary>
|
---|
12 | <secondary>usage</secondary></indexterm>
|
---|
13 |
|
---|
14 | <para>Linux uses a special booting facility named SysVinit. It's based on a
|
---|
15 | concept of <emphasis>run-levels</emphasis>. It can be widely different
|
---|
16 | from one system to another, so it can't be assumed that because things
|
---|
17 | worked in <insert distro name> they should work like that in LFS
|
---|
18 | too. LFS has its own way of doing things, but it respects generally
|
---|
19 | accepted standards.</para>
|
---|
20 |
|
---|
21 | <para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works
|
---|
22 | using a run-levels scheme. There are 7 (from 0 to 6) run-levels
|
---|
23 | (actually, there are more run-levels but they are for special cases and
|
---|
24 | generally not used. The init man page describes those details), and each
|
---|
25 | one of those corresponds to the things the computer is supposed to do when
|
---|
26 | it starts up. The default run-level is 3. Here are the descriptions of the
|
---|
27 | different run-levels as they are often implemented:</para>
|
---|
28 |
|
---|
29 | <literallayout>0: halt the computer
|
---|
30 | 1: single-user mode
|
---|
31 | 2: multi-user mode without networking
|
---|
32 | 3: multi-user mode with networking
|
---|
33 | 4: reserved for customization, otherwise does the same as 3
|
---|
34 | 5: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
|
---|
35 | 6: reboot the computer</literallayout>
|
---|
36 |
|
---|
37 | <para>The command used to change run-levels is <command>init
|
---|
38 | <runlevel></command> where <runlevel> is the target run-level. For
|
---|
39 | example, to reboot the computer, a user would issue the <command>init
|
---|
40 | 6</command> command. The <command>reboot</command> command is just an alias for
|
---|
41 | it, as is the <command>halt</command> command an alias for <command>init
|
---|
42 | 0</command>.</para>
|
---|
43 |
|
---|
44 | <para>There are a number of directories under <filename>/etc/rc.d</filename>
|
---|
45 | that look like like rc?.d (where ? is the number of the run-level) and rcsysinit.d
|
---|
46 | all containing a number of symbolic links. Some begin with a K, the others begin
|
---|
47 | with an S, and all of them have two numbers following the initial letter. The K
|
---|
48 | means to stop (kill) a service, and the S means to start a service. The numbers
|
---|
49 | determine the order in which the scripts are run, from 00 to 99; the lower the
|
---|
50 | number the sooner it gets executed. When init switches to another run-level, the
|
---|
51 | appropriate services get killed and others get started.</para>
|
---|
52 |
|
---|
53 | <para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the
|
---|
54 | symlinks all point to them. Killing links and starting links point to
|
---|
55 | the same script in /etc/rc.d/init.d. That's because the scripts can be
|
---|
56 | called with different parameters like start, stop, restart, reload,
|
---|
57 | status. When a K link is encountered, the appropriate script is run with
|
---|
58 | the stop argument. When an S link is encountered, the appropriate script
|
---|
59 | is run with the start argument.</para>
|
---|
60 |
|
---|
61 | <para>There is one exception. Links that start with an S in the
|
---|
62 | rc0.d and rc6.d directories will not cause anything to be started. They
|
---|
63 | will be called with the parameter <emphasis>stop</emphasis> to stop
|
---|
64 | something. The logic behind it is that when you are going to reboot or
|
---|
65 | halt the system, you don't want to start anything, only stop the
|
---|
66 | system.</para>
|
---|
67 |
|
---|
68 | <para>These are descriptions of what the arguments make the
|
---|
69 | scripts do:</para>
|
---|
70 |
|
---|
71 | <itemizedlist>
|
---|
72 |
|
---|
73 | <listitem><para><emphasis>start</emphasis>: The service is
|
---|
74 | started.</para></listitem>
|
---|
75 |
|
---|
76 | <listitem><para><emphasis>stop</emphasis>: The service is
|
---|
77 | stopped.</para></listitem>
|
---|
78 |
|
---|
79 | <listitem><para><emphasis>restart</emphasis>: The service is
|
---|
80 | stopped and then started again.</para></listitem>
|
---|
81 |
|
---|
82 | <listitem><para><emphasis>reload</emphasis>: The configuration
|
---|
83 | of the service is updated.
|
---|
84 | This is used after the configuration file of a service was modified, when
|
---|
85 | the service doesn't need to be restarted.</para></listitem>
|
---|
86 |
|
---|
87 | <listitem><para><emphasis>status</emphasis>: Tells if the service
|
---|
88 | is running and with which PIDs.</para></listitem>
|
---|
89 |
|
---|
90 | </itemizedlist>
|
---|
91 |
|
---|
92 | <para>Feel free to modify the way the boot process works (after all, it's your
|
---|
93 | own LFS system). The files given here are just an example of how it can be
|
---|
94 | done in a nice way (well, what we consider nice -- you may hate it).</para>
|
---|
95 |
|
---|
96 | </sect1>
|
---|