Edwin van Vliet wrote:
$ cat /etc/rc.d/rc.sysinit
start   mountkernfs
start   udev
start   swap
start   $local_fs
...
$ cat /etc/rc.d/rc.1
stop    $network
...
$

This might be a nice solution, since it will be quite easy to add some lines in the right places once a script is installed, it is easy to maintain, it is clear, and it can be commented. I'll try to make a test case.

Ok, so I have converted my first attempt to a working (awk based) test case, and I have thought of a solution:


If I change the configuration file format to something like this:
$ cat /etc/rc.d/rc.sysinit
start    mountkernfs    "Mounting kernel based file systems"
start    udev           "Starting device daemon"
start    swap           "Activating swap partitions"
start    $local_fs      "Starting local file system facility"
...
$

This would print the following output to screen (e.g. while activating swap partitions):

Mounting kernel based file systems...            [  OK  ]
Starting device daemon...                        [  OK  ]
Activating swap partitions...

All output from the /etc/init.d/* scripts would be logged to a file or, or printed to screen if it is important enough information. It might be a nice idea to make a configuration option for this, of to have it depend on a kernel parameter like 'quiet', which I would like. I don't need to read all the kernel messages at boot time, though others might want to.

Back to an earlier problem: the init "facilities".
For example: the local file system facility might actually consist of a number of scripts from the current lfs-bootscripts package, so having a configuration file that describes the facility's scripts might solve the issue. For example:


$ cat /etc/rc.d/rc.facilities
$local_fs   checkfs mountfs cleanfs
$time       setclock
$

Does anyone have a better idea?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to