source: bootscripts/contrib/lsb-v3/README@ 84ce1e3

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 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 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
Last change on this file since 84ce1e3 was a8a87e6, checked in by DJ Lucas <dj@…>, 14 years ago

Typo fix. Thanks Gilles.

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

  • Property mode set to 100644
File size: 5.4 KB
Line 
1LSB-V3 README
2
3The scripts contained in this directory are a complete rewrite of the
4boot scripts from LFS-6.1 (updated for LFS-SVN about 2010-04-28). As is
5usually the case with a rewrite, there have been many changes:
6
7AS OF 20080907, THESE SCRIPTS REQUIRE THE NEW initd-tools PACKAGE.
8Dan Nicholson has recently released an initd-tools package that contain
9LSB compliant install_initd and remove_initd programs written in C.
10See the INSTALL file for installation instructions.
11
12LSB Version 3.2 Compliant Scripts - Immediately noticable are the LSB headers
13in the rc.d scripts themselves. Each script contains a usable header to
14allow for automating both the installation of, and determining proper
15execution order for the startup scripts. These values can also be used
16directly in parallel boot setups. Additionally, messages are displayed in
17one single write to the screen, after exit status is determined, so that
18they can be used in parallel setups. I am not sure if this was the only
19barrier to auto language translation in the previous bootscripts. Further,
20the messages are created from parts and only written to the screen in a
21single command, so maybe no help at all WRT translated boot messages.
22
23Distribution Independent - this original goal for the LFS scripts has been
24stretched even further by providing both a global rc config file that
25contains (generally) static values, and a new rc.site config file to allow
26customization of messages as diplayed to the end user during the boot
27process. The format of messages printed to the screen is adjustable
28here. As well, the other options that were available in the previous
29versions of the lfs-bootscripts, and additional options as discussed below,
30are configurable by the /etc/sysconfig/rc.site file.
31
32Single Environment - The rc script has been rewritten completely to allow a
33single source of the boot configuration per runlevel change. This config
34is inherited from rc's environment as opposed to being sourced everytime a
35script is run. This results in a negledgable decrease in boot time, but
36it is just better in principle.
37
38Boot Logging - The previous incarnation of the boot log didn't begin
39recording events until the root filesystem was mounted read/write. This has
40been corrected by providing a tempfs mount immediately after init hands
41control to the rc script. The bootlog is generated on the tempfs and then
42passed to the log file before login. Additionally, shutdown events are no
43longer recorded in the bootlog. They were pretty much useless and it really
44wasn't what I'd call a *boot* log. Boot logging is on by default and is
45configurable in the /etc/sysconfig/rc.site file.
46
47Interactive Boot - This feature has been included by default, and is a
48little more polished than my previous attempt. It does introduce a two
49second delay in the boot process (so that you have time to press a button
50to select interactive mode). This time value, and the option prompt itself,
51is configurable in the /etc/sysconfig/rc.site file.
52
53Path changes - The base directory for the bootscripts is now /etc, not
54/etc/rc.d. This is mostly to conform with mainstream distros, but other
55boot methods do expect that /etc/init.d is the location of bootscripts.
56Some distros provide a rc.d direcorty with symlinks to the rc*.d and init.d
57directories, I have not done that. /etc is the location now, get your
58flying fingers accustomed to it! Of course, this is still configurable in
59/etc/sysconfig/rc.site, and if the change is too great, I'll put it back.
60I've also removed the rcsysinit.d directory and replaced it with rcS.d.
61
62LSB Functions - The previous lfs-bootscripts sourced a functions file
63located at /etc/rc.d/init.d/functions. This file has been renamed
64$distro-functions to segregate it from the old. The name is configurable
65by the rc.site configuration file. LSB defined functions are used where
66possible, but the $distro-functions file provides, easy to use wraper
67functions that start/stop/reload/force-reload/restart programs, evaluate
68the numerical LSB return values, and print status messages to the screen.
69Both LFS functions and LSB functions are documented directly in the scritps
70located at /etc/init.d/$distro-functions and /lib/lsb/init-functions
71respectively.
72
73Pretier - Yeah, I just couldn't handle all the grey text... By default,
74successful boot messages are prefixed with a single green astrik character,
75warning messages with two yellow astirks, and failures are prefixed with
76three red astriks. This just provides a second 'quick glance' status when
77watching the boot messages fly by. Again, the prefixes are configurable (or
78completely removable) in the /etc/sysconfig/rc.site file.
79
80Complete Rewrite - Yep. That doesn't mean that code wasn't reused when
81possible, so Alexander, Bryan, Dan, Gerard, Jeremy, Jim, Mathias, Matthew,
82Nathan, and countless other contributors (whose names I've forgotten and will
83promptly be reminded of (please)) are due credit for these as well. That
84said, at very least, this is a complete reorganisation that I've tested to
85the best of my ability, but there probably are some hidden bugs that will
86come to lite when used more frequently. Please give me a shout _when_ you
87find them.
88
89The sysctl script runs much earlier in the boot process, as a result, it
90negates the need for the consolelog script. Set 'kernel.printk = X' in your
91/etc/sysctl.conf file for equivalent functionality.
92
93Thanks.
94
95-- DJ Lucas
96dj@linuxfromscratch.org
97
Note: See TracBrowser for help on using the repository browser.