[arch-general] [arch-dev-public] [signoff] udev 118-2

Xavier shiningxc at gmail.com
Sat Feb 23 17:34:25 EST 2008

On Sat, Feb 23, 2008 at 11:09:03PM +0100, Michal Soltys wrote:
> Michal Soltys wrote:
>> As for your #3 idea, you can store that blacklist file in i.e. 
>> /dev/.udev/blacklist, which you can remove later, after udev processing.
>> Also, rc.sysinit script you could add extra trigger pass for failed 
>> events, i.e.
> Actually, let it stay there. /dev/.udev/ is always present after udevd is 
> started, and is never removed. So just generate the blacklist early in 
> rc.sysinit, like you suggested, and keep it there - this way it can be 
> reused whenever script responsbile for loading modules is called.

What if you blacklist a module after booting, then plug in some hardware?

The previous udev package still looks like the most acceptable way.

More information about the arch-general mailing list