[EMAIL PROTECTED] wrote: >So hw-detect has all sorts of code to give the user control over what >modules are loaded and with what parameters, and to pass those along to >the installed system even, but this is all sidestepped by udev which >just does whatever it feels like during boot. I don't know how we can >possibly fix this. Somehow delay udev from running until hw-detect? If the problem is only passing parameters from the kernel command line then you can solve this with a script which parses it and writes the parameters to a file in /etc/modprobe.d/. If there is a good reason to have udev load the modules for different classes of devices at different times then this can be arranged too, look at /sbin/udevsynthesize for the general idea.
-- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
