Toralf Lund wrote: > Mikkel L. Ellertson wrote: > >> >> In that case, you are probably going to have to boot from a >> rescue CD. In single user mode, the network in not supposed to >> be initialized. > > The problem is, it seems, that "network hardware init" is done a lot > earlier in the boot sequence than the actual network startup, and > includes some ifconfig or iwconfig calls, which is what breaks > everything in my case. In fact, this step is done even for networks that > have ONBOOT=no. Qlearly, a related question is why things have been done > this way. Shouldn't the network config be left alone until it is time to > start the network? And shouldn't disabled configs (as in ONBOOT=no) be > skipped completely? > It depends on how the modules are loaded. If they are loaded because of an alias in /etc/modprobe.conf, then the hardware should not get initialed. If the modules is loaded by modprobe.conf, HAL, or by hotplug, that is another story. Just loading the module should not result in calls to ifconfig or iwconfig. In any case, using init=/bin/bash from Grub should skip all that. It drops you to a command prompt without running scripts. (Bash is run instead of init.) Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
