| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293 | LSB-V3 READMEThe scripts contianed in this directory are a complete rewrite of theboot scripts from LFS-6.1 (updated for LFS-SVN about 2008-05-31).  As isusually the case with a rewrite, there have been many changes:AS OF 20080907, THESE SCRIPTS REQUIRE THE NEW initd-tools PACKAGE.Dan Nicholson has recently released an initd-tools package that contain LSB compliant install_initd and remove_initd programs written in C.See the INSTALL file for installation instructions.LSB Version 3.2 Compliant Scripts - Immediately noticable are the LSB headersin the rc.d scripts themselves.  Each script contains a usable header toallow for automating both the installation of, and determining properexecution order for the startup scripts.  These values can also be useddirectly in parallel boot setups.  Additionally, messages are displayed inone single write to the screen, after exit status is determined, so thatthey can be used in parallel setups.  I am not sure if this was the onlybarrier to auto language translation in the previous bootscripts.  Further,the messages are created from parts and only written to the screen in asingle command, so maybe no help at all WRT translated boot messages.Distribution Independent - this original goal for the LFS scripts has beenstretched even further by providing both a global rc config file thatcontains (generally) static values, and a new rc.site config file to allowcustomization of messages as diplayed to the end user during the bootprocess.  The format of messages printed to the screen is adjustablehere.  As well, the other options that were available in the previousversions of the lfs-bootscripts, and additional options as discussed below,are configurable by the /etc/sysconfig/rc.site file.Single Environment - The rc script has been rewritten completely to allow asingle source of the boot configuration per runlevel change.  This configis inherited from rc's environment as opposed to being sourced everytime ascript is run.  This results in a negledgable decrease in boot time, butit is just better in principle.Boot Logging - The previous incarnation of the boot log didn't beginrecording events until the root filesystem was mounted read/write.  This hasbeen corrected by providing a tempfs mount immediately after init handscontrol to the rc script.  The bootlog is generated on the tempfs and thenpassed to the log file before login.  Additionally, shutdown events are nolonger recorded in the bootlog.  They were pretty much useless and it reallywasn't what I'd call a *boot* log.  Boot logging is on by default and isconfigurable in the /etc/sysconfig/rc.site file.Interactive Boot - This feature has been included by default, and is alittle more polished than my previous attempt.  It does introduce a twosecond delay in the boot process (so that you have time to press a buttonto select interactive mode).  This time value, and the option prompt itself,is configurable in the /etc/sysconfig/rc.site file.Path changes - The base directory for the bootscripts is now /etc, not/etc/rc.d.  This is mostly to conform with mainstream distros, but otherboot methods do expect that /etc/init.d is the location of bootscripts.Some distros provide a rc.d direcorty with symlinks to the rc*.d and init.ddirectories, I have not done that.  /etc is the location now, get yourflying fingers accustomed to it!  Of course, this is still configurable in/etc/sysconfig/rc.site, and if the change is too great, I'll put it back.I've also removed the rcsysinit.d directory and replaced it with rcS.d.LSB Functions - The previous lfs-bootscripts sourced a functions filelocated at /etc/rc.d/init.d/functions.  This file has been renamed$distro-functions to segregate it from the old. The name is configurableby the rc.site configuration file.  LSB defined functions are used wherepossible, but the $distro-functions file provides, easy to use wraperfunctions that start/stop/reload/force-reload/restart programs, evaluatethe numerical LSB return values, and print status messages to the screen.Both LFS functions and LSB functions are documented directly in the scritpslocated at /etc/init.d/$distro-functions and /lib/lsb/init-functionsrespectively.Pretier - Yeah, I just couldn't handle all the grey text...  By default,successful boot messages are prefixed with a single green astrik character,warning messages with two yellow astirks, and failures are prefixed withthree red astriks.  This just provides a second 'quick glance' status whenwatching the boot messages fly by.  Again, the prefixes are configurable (orcompletely removable) in the /etc/sysconfig/rc.site file.Complete Rewrite - Yep.  That doesn't mean that code wasn't reused whenpossible, so Alexander, Bryan, Dan, Gerard, Jeremy, Jim, Mathias, Matthew,Nathan, and countless other contributors (whose names I've forgotten and willpromptly be reminded of (please)) are due credit for these as well.  Thatsaid, at very least, this is a complete reorganisation that I've tested tothe best of my ability, but there probably are some hidden bugs that willcome to lite when used more frequently.  Please give me a shout _when_ youfind them.Thanks.-- DJ Lucasdj@linuxfromscratch.org
 |