2008/2/23, Aaron Griffin <[EMAIL PROTECTED]>: > Ok, guys - honest question. Because udev is being a big pain in the > ass with the way we do module blacklisting, we might want to > reevaluate it. > > Right now we support blacklisting of modules in rc.conf, in addition > to a kernel param disablemodules=x,y,z > > Udev autoloading is controlled by MOD_AUTOLOAD and the load_modules > kernel param. > > We *can* use modprobe based blacklisting here, but we lose the above > items. blacklisting will be controlled only by /etc/modprobe.conf (and > modprobe.d/*) and we lose the ability to shut it off via rc.conf. > > What do we gain? Speed and simplicity. No extraneous scripts to handle > this stuff, and all that jazz. > > This is how fast this script was when I originally wrote it: > http://img.phraktured.net/other/udev_modules_boot.png > Now it apparently takes 3 times as long due to all the added blacklisting > cruft > > What do we lose? Robustness. > See below for an explanation of the blacklist changes >
+1 for keeping things in rc.conf Maybe I've missed the point of all this udev slowdown thing, but since udev-116 was considered faster by those users who reported udev-118 slowness - I guess this change caused it: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/udev/load-modules.sh.diff?r1=1.9&r2=1.10&cvsroot=Core&only_with_tag=TESTING if so - cannot it be just reverted and see what the difference is? -- Roman Kyrylych (Роман Кирилич)