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 -- [email protected] mailing list
