mess-mate wrote:
Hi
anybody know where/how bash is loaded at INIT ??
or for what scripts INIT is looking before 'mountkernfs' ?
best regards
Is this still the same reoccurring problem? If so it probably should
have not jumped topics and still belongs on LFS-Support...anyway. First
thing you need to do is figure out which script has the problem. I'm
not sure I understood the question correctly, so if this is too
simplified just ignore the rest of this message.
The scripts run in sequential order....first all the symlinks in
/etc/rc.d/rcsysinit.d/. The K scripts are run first in alphanumerical
order, then the S scripts, again in alphanumerical order. Next is
passed to the default runlevel (3 by default LFS) so that the scripts
linked to in /etc/rc.d/rc3.d/ are run. The real scripts reside in
/etc/rc.d/init.d/.
If this is still the same problem, there is a little something in
contrib to help you identify where the problem is. If using version
3.2.1 of the lfs-bootscripts, do the following from your sources directory:
cp /etc/sysconfig/rc /etc/sysconfig/rc.backup &&
cp /etc/rc.d/init.d/rc /etc/rc.d/init.d/rc.backup &&
cp lfs-bootscripts-3.2.1/contrib/init.d/rc-Interactive \
/etc/rc.d/init.d/rc &&
cp lfs-bootscripts-3.2.1/contrib/sysconfig/rc-Interactive \
/etc/sysconfig/rc &&
chown root:root /etc/rc.d/init.d/rc /etc/sysconfig/rc &&
chmod 754 /etc/rc.d/init.d/rc &&
chmod 640 /etc/sysconfig/rc
Now reboot and press "I" when prompted, this will definitely identify
the problem script, assuming you don't have a read-only root partition.
The alternate rc script will echo the script name in interactive mode
before executing it. Once the failing script is identified, the next
step is to throw in a whole bunch of echo statements so you know exactly
where the error occurs (if you can't immediately tell by looking at the
script). These steps will get us much closer to the problem. For
instance lets say we have the following lines in the script....
-------------------
start)
echo "Starting some daemon..."
some_daemon -some_parameter -more_parameters
evaluate_retval
;;
-------------------
That should become:
-------------------
start)
echo "######## Entered the start case!"
echo "Starting some daemon..."
some_daemon -some_parameter -more_parameters
echo "######## This is after the action line in the script!"
evaluate_retval # This will always pass now because the echo
# above was successful
echo "######## We made it through to completion
;;
--------------------
When you are done with your troubleshooting, you can return to the
original rc script and config file. Now having dispersed all that, I
can all but guarantee that your problem lies in a missing variable in a
config file someplace as pointed out by Uli earlier in the previous thread.
I hope that gets you a little closer to the problem.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
