removed c7-createdirs

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1439 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2002-01-15 21:08:26 +00:00
parent 1740d4852d
commit d535079aca
5 changed files with 16 additions and 41 deletions

View File

@ -1,5 +1,5 @@
<chapter id="chapter07"> <chapter id="chapter07">
<title>Creating system boot scripts</title> <title>Setting up system boot scripts</title>
<?dbhtml filename="chapter07.html" dir="chapter07"?> <?dbhtml filename="chapter07.html" dir="chapter07"?>
&c7-introduction; &c7-introduction;

View File

@ -1,13 +0,0 @@
<sect1 id="ch07-createdirs">
<title>Creating directories</title>
<?dbhtml filename="createdirs.html" dir="chapter07"?>
<para>We need to start by creating a few extra directories that are used by
the boot scripts. These directories are created by running:</para>
<para><screen><userinput>cd /etc &amp;&amp;</userinput>
<userinput>mkdir rc{0,1,2,3,4,5,6,S}.d init.d sysconfig &amp;&amp;</userinput>
<userinput>cd init.d</userinput></screen></para>
</sect1>

View File

@ -2,12 +2,10 @@
<title>Introduction</title> <title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter07"?> <?dbhtml filename="introduction.html" dir="chapter07"?>
<para>This chapter will create the necessary scripts that are run at boot time. <para>This chapter will setup the bootscripts that you installed in chapter
These scripts perform tasks such as remounting the root file system 6. Most of these scripts will work without needing to modify them, but a
mounted read-only by the kernel into read-write mode, activating the swap few do require additional configuration files setup as they deal with
partition(s), running a check on the root file system to make sure it's hardware dependant information.</para>
intact, setting up networking and starting the daemons that the
system uses.</para>
<para>We will be using SysV style init scripts. We have chosen this style <para>We will be using SysV style init scripts. We have chosen this style
because it is widely used and we feel comfortable with it. If you want to because it is widely used and we feel comfortable with it. If you want to
@ -16,10 +14,5 @@ at <ulink
url="&hints-root;bsd-init.txt">&hints-root;bsd-init.txt</ulink> url="&hints-root;bsd-init.txt">&hints-root;bsd-init.txt</ulink>
.</para> .</para>
<para>If you decided to copy&amp;paste the scripts from this chapter, you
would do best to copy&amp;paste them in small chunks, one screenfull at a
time. Some scripts are too large to fit in the copy buffer and will be
truncated when you paste it.</para>
</sect1> </sect1>

View File

@ -31,23 +31,19 @@ the target runlevel. For example, to reboot the computer, a user would issue
the init 6 command. The reboot command is just an alias, as is the halt the init 6 command. The reboot command is just an alias, as is the halt
command an alias to init 0.</para> command an alias to init 0.</para>
<para>The /etc/init.d/rcS script is run at every startup of the computer, <para>There are a number of directories under /etc/rc.d that look like
before any runlevel is executed and runs the scripts listed in like rc?.d where ? is the number of the runlevel and rcsysinit.d which
/etc/rcS.d</para> contain a number of symbolic links. Some begin with an K, the others
begin with an S, and all of them have three numbers following the initial
letter. The K means to stop (kill) a service, and the S means to start a
service. The numbers determine the order in which the scripts are run,
from 00 to 99; the lower the number the sooner it gets executed. When init
switches to another runlevel, the appropriate services get killed and
others get started.</para>
<para>There are a number of directories under /etc that look like like rc?.d <para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the
where ? is the number of the runlevel and rcS.d which contain a number of
symbolic links. Some begin with an K, the others begin with an S, and all
of them have three numbers following the initial letter. The K means to
stop (kill) a service, and the S means to start a service. The numbers
determine the order in which the scripts are run, from 000 to 999; the
lower the number the sooner it gets executed. When init switches to
another runlevel, the appropriate services get killed and others get
started.</para>
<para>The real scripts are in /etc/init.d. They do all the work, and the
symlinks all point to them. Killing links and starting links point to symlinks all point to them. Killing links and starting links point to
the same script in /etc/init.d. That's because the scripts can be the same script in /etc/rc.d/init.d. That's because the scripts can be
called with different parameters like start, stop, restart, reload, called with different parameters like start, stop, restart, reload,
status. When a K link is encountered, the appropriate script is run with status. When a K link is encountered, the appropriate script is run with
the stop argument. When a S link is encountered, the appropriate script the stop argument. When a S link is encountered, the appropriate script

View File

@ -332,7 +332,6 @@
<!ENTITY chapter7 SYSTEM "chapter7/chapter7.xml"> <!ENTITY chapter7 SYSTEM "chapter7/chapter7.xml">
<!ENTITY c7-introduction SYSTEM "chapter7/introduction.xml"> <!ENTITY c7-introduction SYSTEM "chapter7/introduction.xml">
<!ENTITY c7-usage SYSTEM "chapter7/usage.xml"> <!ENTITY c7-usage SYSTEM "chapter7/usage.xml">
<!ENTITY c7-createdirs SYSTEM "chapter7/createdirs.xml">
<!ENTITY c7-rc SYSTEM "chapter7/rc.xml"> <!ENTITY c7-rc SYSTEM "chapter7/rc.xml">
<!ENTITY c7-rcS SYSTEM "chapter7/rcS.xml"> <!ENTITY c7-rcS SYSTEM "chapter7/rcS.xml">
<!ENTITY c7-functions SYSTEM "chapter7/functions.xml"> <!ENTITY c7-functions SYSTEM "chapter7/functions.xml">