Changeset d535079
- Timestamp:
- 01/15/2002 09:08:26 PM (22 years ago)
- Branches:
- 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, 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_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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 67eb804
- Parents:
- 1740d48
- Files:
-
- 1 deleted
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/chapter07.xml
r1740d48 rd535079 1 1 <chapter id="chapter07"> 2 <title> Creatingsystem boot scripts</title>2 <title>Setting up system boot scripts</title> 3 3 <?dbhtml filename="chapter07.html" dir="chapter07"?> 4 4 -
chapter07/introduction.xml
r1740d48 rd535079 3 3 <?dbhtml filename="introduction.html" dir="chapter07"?> 4 4 5 <para>This chapter will create the necessary scripts that are run at boot time. 6 These scripts perform tasks such as remounting the root file system 7 mounted read-only by the kernel into read-write mode, activating the swap 8 partition(s), running a check on the root file system to make sure it's 9 intact, setting up networking and starting the daemons that the 10 system uses.</para> 5 <para>This chapter will setup the bootscripts that you installed in chapter 6 6. Most of these scripts will work without needing to modify them, but a 7 few do require additional configuration files setup as they deal with 8 hardware dependant information.</para> 11 9 12 10 <para>We will be using SysV style init scripts. We have chosen this style … … 17 15 .</para> 18 16 19 <para>If you decided to copy&paste the scripts from this chapter, you20 would do best to copy&paste them in small chunks, one screenfull at a21 time. Some scripts are too large to fit in the copy buffer and will be22 truncated when you paste it.</para>23 24 17 </sect1> 25 18 -
chapter07/usage.xml
r1740d48 rd535079 32 32 command an alias to init 0.</para> 33 33 34 <para>The /etc/init.d/rcS script is run at every startup of the computer, 35 before any runlevel is executed and runs the scripts listed in 36 /etc/rcS.d</para> 34 <para>There are a number of directories under /etc/rc.d that look like 35 like rc?.d where ? is the number of the runlevel and rcsysinit.d which 36 contain a number of symbolic links. Some begin with an K, the others 37 begin with an S, and all of them have three numbers following the initial 38 letter. The K means to stop (kill) a service, and the S means to start a 39 service. The numbers determine the order in which the scripts are run, 40 from 00 to 99; the lower the number the sooner it gets executed. When init 41 switches to another runlevel, the appropriate services get killed and 42 others get started.</para> 37 43 38 <para>There are a number of directories under /etc that look like like rc?.d 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 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> 47 48 <para>The real scripts are in /etc/init.d. They do all the work, and the 44 <para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the 49 45 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 be46 the same script in /etc/rc.d/init.d. That's because the scripts can be 51 47 called with different parameters like start, stop, restart, reload, 52 48 status. When a K link is encountered, the appropriate script is run with -
index.xml
r1740d48 rd535079 333 333 <!ENTITY c7-introduction SYSTEM "chapter7/introduction.xml"> 334 334 <!ENTITY c7-usage SYSTEM "chapter7/usage.xml"> 335 <!ENTITY c7-createdirs SYSTEM "chapter7/createdirs.xml">336 335 <!ENTITY c7-rc SYSTEM "chapter7/rc.xml"> 337 336 <!ENTITY c7-rcS SYSTEM "chapter7/rcS.xml">
Note:
See TracChangeset
for help on using the changeset viewer.