Red Hat Bugzilla – Bug 26312
ONBOOT=no is not working
Last modified: 2007-04-18 12:31:14 EDT
I have initscripts 5.61.1 installed and with ONBOOT=no, networking on eth0 is still started on bootup
Is it pcmcia?
hotplug is being nice enough to load it for you. Bleah.
Standard PCI network interface?
Yup. I just reproduced it here; basically, if you have ONBOOT=no and you boot an entire system, *something* triggers a hotplug event that loads the driver.
Please try the freshest Rawhide, I can't reproduce this with such a system - I had to manually ifup the interface (and restart autofs, as I discovered later)
Happens for me with a normal machine with dhcp and ONBOOT=no with the current rpms as of 5 minutes ago. No pcmcia in this computer.
Still happens with hotplug-2001_02_14-3. Need to look more into this.
When a module is loaded, the kernel asks hotplug to initialize it and it does what it's told.
hotplugging should be turned off when the initscript loads the modules - it does so to preserve ordering, and this obiviously calls hotplug.
Actually, the more I think about it, the fact that hotplug triggers for every interface creation, regardless of cause, is fundamentally broken. We should just remove the package until it's done right, or fix it. It's like hacking the initscripts to work around linuxconf being a pile of dung.
In short: interface creation does not, and *should not*, imply that you want to bring up the interface, regardless of device type.
That would be kernel related... and we would to make it continue working when plugging in a new device, like USB ethernet.
*** Bug 28191 has been marked as a duplicate of this bug. ***
That is not a kernel problem. hotplug gets all the events, and it needs to have the brains to know what to do with them (and be more configurable in this regard.) Policy goes in userspace, not in kernel space.
This should be fixed in initscripts-5.67-1.