Hi, According to /etc/rc.d/README At boot time, the boot level master script /etc/init.d/boot is called to initialise the system (e.g. file system check, ...). It also executes some hardware init scripts linked into /etc/init.d/boot.d/. Then it calls /etc/init.d/boot.local, which executes the local commands. So just to give a snip of it some of the files are as follows /etc/init.d/boot /etc/init.d/boot.clock /etc/init.d/boot.crypto /etc/init.d/boot.idedma /etc/init.d/boot.ipconfig /etc/init.d/boot.klog /etc/init.d/boot.ldconfig /etc/init.d/boot.local /etc/init.d/boot.localfs /etc/init.d/boot.localnet /etc/init.d/boot.lvm /etc/init.d/boot.proc /etc/init.d/boot.restore_permissions /etc/init.d/boot.setup /etc/init.d/boot.swap /etc/init.d/boot.sysctl I want to copy the configuration files from the floopy by using a the following command mount /dev/fd0 /mnt/floppy if [ $? -eq 0 ] then cp -a -f /mnt/floppy/* / umount /mnt/floppy For some reason my brain says /etc/init.d/boot.local is to late for that as one of the configuration files is /etc/fstab along with various other /etc/sysconfig files. taken from /etc/init.d/boot script ##### # start bootup client scripts. # if test -d /etc/init.d/boot.d/ ; then for i in /etc/init.d/boot.d/S*; do test -f $i || continue if test -x "$i" ; then # Active boot scripts, should have their own messages $i start else # Old boot scripts, may not have any message echo Running $i /bin/sh $i b rc_status -v1 -r fi done fi ### So I came to the conclusion that I need to create a init script based on /etc/init.d/skeleton but lack of good quality coffee has caused cerebral inactivity. Would boot.proc be the line or boot.idedma for the following so my configuration files can be copied from the floopy to the system #Required-Start: Thanks -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
On Tuesday 23 July 2002 19.17, Togan Muftuoglu wrote:
Would boot.proc be the line or boot.idedma for the following so my configuration files can be copied from the floopy to the system
#Required-Start:
I think you should put your script in the Required-Start line of every other script that depends on the configuration files you're copying. I don't think your script needs any of the other scripts to run, so you shouldn't need to have anything in your script's require-start. //Anders
participants (2)
-
Anders Johansson
-
Togan Muftuoglu