Jon Nettleton (jon.nettleton(a)gmail.com) said:
> Sure. I just don't see what you gain by replacing a shell
> loads modules... with a different shell script.
I think the big win with changes like this is consistency. Right now
there are 5 differents methods for loading modules on startup.
1) initrd. Of course this is necessary, but mkinitrd it doesn't
respect changes made to /etc/modprobe.d/blacklist.
Really? modprobe --show-depends pulls in things from the blacklist?
Sounds like a bug.
Should probably be nuked - it's time for it to go.
4) some modules right in /etc/rc.sysinit
Already removed in CVS.
5) and the new guy /etc/sysconfig/modules
Not that new. It's 2 1/2 years old.