Near the start of rc.sysinit, I put: exec /sbin/lanpup-main.
The error: can't find usr_cram.fs file, still came up, so I replaced it with just my code & it still comes up!
I looked for other scripts that had the error & found none.
Is this error hard coded into BusyBox?
BusyBox is run by init, & I don't know what runs rc.sysinit.
What besides rc.sysinit shows boot errors (SOLVED)
What besides rc.sysinit shows boot errors (SOLVED)
Last edited by sunburnt on Sat 03 Dec 2005, 16:39, edited 2 times in total.
-
Guest
Yes, I've made a new image.gz & booted from it, the new rc.sysinit file is in /root0/.etc/rc.d in image.gz.
I've got PizzaPup LANbooting, but it's not reading all the commands it seems, it works if I type them in.
The main wonderment is, most all of rc.sysinit is wiped out & it still gives the same errors.
With rc.local0 & rc.network not running, what's the script that's generating the error print outs?
I can't see any scripts that are left, /sbin/init doesn't have the error in it, I looked, not there.
I've got PizzaPup LANbooting, but it's not reading all the commands it seems, it works if I type them in.
The main wonderment is, most all of rc.sysinit is wiped out & it still gives the same errors.
With rc.local0 & rc.network not running, what's the script that's generating the error print outs?
I can't see any scripts that are left, /sbin/init doesn't have the error in it, I looked, not there.
you can put trace statements in a script to see if it's doing what you think it's doing
for example:
echo 'here 10'
if it displays too fast, you could do something like:
echo 'here 20'
sleep 20
or you could pause and wait until the enter key is pressed:
read -p 'here 30 in rc.sysinit - press enter' xxyy
for example:
echo 'here 10'
if it displays too fast, you could do something like:
echo 'here 20'
sleep 20
or you could pause and wait until the enter key is pressed:
read -p 'here 30 in rc.sysinit - press enter' xxyy