Failure of one boot script keeps others from running

[MackS]

Howdy

Something funky happens when booting gentoo. If my laptop isn't connected to the network, /etc/init.d/net.eth0 (which is configured to contact a DHCP server) fails. That's something I can understand. However, if /etc/init.d/net.eth0 fails all the other boot scripts which are usually run after it don't get invoked. This means, besides other things, that if my laptop isn't connected to the network at boot time cupsd isn't started, and I can't print without manually running the appropriate script.

Should the boot procedure use this "domino"-style error handling? Is it really meant to work that way? If so, is there a way to make the failure of one boot script NOT affect the execution of the remaining ones?

Thank you for any help

Mark

[lx]

Well packages are depending on "net", so either rip it out or change net to not fail. in other words change the net.eth0 bootscript. Maybe this will fix it.

Cya lX.
_________________
"Remember there's a big difference between kneeling down and bending over.", Frank Zappa

[MackS]

You are right, thank you for pointing it out for me.

Thanks
Mack