Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Wed, 2006-12-13 at 12:25 -0800, Greg KH wrote: > > Here's a question, then. Is there a way, after boot, to cause udev to > > attempt to detect and load modules? Basically, is there a way to > > emulate the old behavior of the "coldplug" init script? This would be > > very useful for our LiveCD builds, since we've lost the ability to do > > "nohotplug" on the command line to disable cold plugging. > > You can re-run /sbin/udevtrigger if you want to. Nice. > But why do it later? Why not just let udev do it at the start of boot? Well, it's pretty simple, we don't always want udev to do it. > What do you gain by delaying this? Delaying? Nothing. Allowing it to be disabled from the kernel command line is what I am looking for, here. Basically, we would disable udev cold plugging by default. Then, when we're actually to the point of being a bit more in control of the system, we check the kernel command line. If "nohotplug" is there, we do nothing. If it isn't, then we'd run /sbin/udevtrigger. This would "coldplug" the devices, but still allow us to retain functionality that we used to have with older coldplug versions. The only issue that we're now facing is that to disable coldplug also disables their services being auto-started, which means that even if we do run udevtrigger later, the services for those devices won't be started. I'm sure there's some solution to this, but this is really why I've been dreading newer udev versions going stable. While the newer versions are better, no doubt, it means we have to rethink how most of the auto-detection and configuration is done on the LiveCD. There have been many times where coldplug tried to load a driver that caused problems for the user, and being able to disable that driver being loaded has allowed them to continue to boot. With a coldplug that cannot be disabled arbitrarily, we cannot do this. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Wed, Dec 13, 2006 at 03:14:56PM -0500, Chris Gianelloni wrote: > On Wed, 2006-12-13 at 10:21 -0800, Greg KH wrote: > > > what's the best way to just completely disable udev coldplug-like > > > module loading? > > > # NOTE: This also affects module coldplugging in udev-096 and higher > > # If you want module coldplugging but not coldplugging of services then you > > # can set RC_COLDPLUG="yes" and RC_PLUG_SERVICES="!*" > > > > so just set RC_COLDPLUG="no" and you will disable the module loading by > > udev at boot time. > > Here's a question, then. Is there a way, after boot, to cause udev to > attempt to detect and load modules? Basically, is there a way to > emulate the old behavior of the "coldplug" init script? This would be > very useful for our LiveCD builds, since we've lost the ability to do > "nohotplug" on the command line to disable cold plugging. You can re-run /sbin/udevtrigger if you want to. But why do it later? Why not just let udev do it at the start of boot? What do you gain by delaying this? thanks, greg k-h -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Wed, 2006-12-13 at 10:21 -0800, Greg KH wrote: > > what's the best way to just completely disable udev coldplug-like > > module loading? > # NOTE: This also affects module coldplugging in udev-096 and higher > # If you want module coldplugging but not coldplugging of services then you > # can set RC_COLDPLUG="yes" and RC_PLUG_SERVICES="!*" > > so just set RC_COLDPLUG="no" and you will disable the module loading by > udev at boot time. Here's a question, then. Is there a way, after boot, to cause udev to attempt to detect and load modules? Basically, is there a way to emulate the old behavior of the "coldplug" init script? This would be very useful for our LiveCD builds, since we've lost the ability to do "nohotplug" on the command line to disable cold plugging. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Wed, Dec 13, 2006 at 04:07:51PM +0100, Wolfram Schlich wrote: > * Greg KH <[EMAIL PROTECTED]> [2006-12-01 18:08]: > > [...] > > If you rely on the specific loading order of modules, you were the crazy > > one in the first place :) > > > > As others have said, look at using udev to name your network devices in > > a persistant manner, it's the best solution. > > > > Or you can just blacklist the modules, and then load them yourself in > > your modules startup location. > > > > The problem with doing this is the modules.d stuff is still broken for > > blacklisting, it will only work on the first reboot of the system, > > there's an open bug for this issue :( > > Greg, > > what's the best way to just completely disable udev coldplug-like > module loading? as per /etc/conf.d/rc: # Dynamic /dev managers can trigger coldplug events which cause services to # start before we are ready for them. If this happens, we can defer these # services to start in the boot runlevel. Set RC_COLDPLUG="no" if you don't # want this. # NOTE: This also affects module coldplugging in udev-096 and higher # If you want module coldplugging but not coldplugging of services then you # can set RC_COLDPLUG="yes" and RC_PLUG_SERVICES="!*" so just set RC_COLDPLUG="no" and you will disable the module loading by udev at boot time. thanks, greg k-h -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
* Greg KH <[EMAIL PROTECTED]> [2006-12-01 18:08]: > [...] > If you rely on the specific loading order of modules, you were the crazy > one in the first place :) > > As others have said, look at using udev to name your network devices in > a persistant manner, it's the best solution. > > Or you can just blacklist the modules, and then load them yourself in > your modules startup location. > > The problem with doing this is the modules.d stuff is still broken for > blacklisting, it will only work on the first reboot of the system, > there's an open bug for this issue :( Greg, what's the best way to just completely disable udev coldplug-like module loading? TIA. -- Regards, Wolfram Schlich <[EMAIL PROTECTED]> Gentoo Linux * http://dev.gentoo.org/~wschlich/ -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Fri, Dec 01, 2006 at 03:40:33PM +0100, Sven K?hler wrote: > Hi, > > when does udev load all the modules and does coldplug? When it first runs. > Is it happening before /etc/init.d/modules? Yes. > If yes, than i would like to shout: are you crazy? Of course, I wouldn't be doing this work if I wasn't :) > Well, until udev became stable, /etc/modules.autoload.d/kernel-2.? was a > good place, to load modules in a specific order - before coldplug. > > Unfortunatly, the order of loading of modules defines the ordner of the > network-interfaces (if you different types of network cards). If you rely on the specific loading order of modules, you were the crazy one in the first place :) As others have said, look at using udev to name your network devices in a persistant manner, it's the best solution. Or you can just blacklist the modules, and then load them yourself in your modules startup location. The problem with doing this is the modules.d stuff is still broken for blacklisting, it will only work on the first reboot of the system, there's an open bug for this issue :( Hope this helps, greg k-h -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Fri, 01 Dec 2006 15:40:33 +0100 Sven Köhler <[EMAIL PROTECTED]> wrote: > Unfortunatly, the order of loading of modules defines the ordner of > the network-interfaces (if you different types of network cards). This is what udev's interface renaming capability is for. Define names for your interfaces according to their MAC address, for example, and all is good. It's also more reliable than relying on the order of module loading to get it right. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] udev coldplugging and /etc/init.d/modules
On Fri, 01 Dec 2006 15:40:33 +0100, Sven Köhler wrote: > Unfortunatly, the order of loading of modules defines the ordner of the > network-interfaces (if you different types of network cards). You can use udev to name the interfaces, which is far less kludgy than relying on the order in which modules are loaded. -- Neil Bothwick "There are no stupid questions, just too many inquisitive idiots." signature.asc Description: PGP signature
[gentoo-dev] udev coldplugging and /etc/init.d/modules
Hi, when does udev load all the modules and does coldplug? Is it happening before /etc/init.d/modules? If yes, than i would like to shout: are you crazy? Well, until udev became stable, /etc/modules.autoload.d/kernel-2.? was a good place, to load modules in a specific order - before coldplug. Unfortunatly, the order of loading of modules defines the ordner of the network-interfaces (if you different types of network cards). So can you imagine, loading the modules before udev's coldplug happens? Greetings, Sven signature.asc Description: OpenPGP digital signature
