On Thu, 2005-06-30 at 19:13 +0200, Joern Abatz wrote: > I think we are in the middle of a process. The old way was: A program talks > to a device file, the kernel wakes up and loads the corresponding module. > The new way is: Something, a boot script, loads a module, udev sees it and > creates the corresponding device file. Maybe some drivers are already living > in the future, so they don't know the old way anymore, and some other > drivers don't know of the future yet, and we are caught in the middle, as we > alway are.
I think the problems are with modules that don't correspond in any way to physical devices, e.g ppp, iptables, maybe some filesystems. Used to be that some of those got loaded automatically (particularly if they corresponded to a /dev entry), but not any more. Anything hardware related is supposed to be loaded by the hotplug infrastructure, and in my experience that works pretty well - in my case, drivers for audio, networking (wired and wireless), usb, video, etc are all loaded without me doing anything. Even the latest nVidia binary drivers seem to hotplug now - I used to load those with some work in modprobe.conf, but I don't even have a modprobe.conf anymore. Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
