Oded Arbel wrote:

Basicly devfsd gets rid of the mess that /dev is and simply does not show you nodes for hardware you don't have (no more 200 /dev/ttyS* nodes when you only have one serial ports) and does away with the single huge list that makes it hard to find what you want.

The problem is not program with hardwired device locations. The problem is devices for which there is still no driver loaded, despite the fact that they are in your system.

Allow me to explain. In the "/dev" method, you could define any access to a particular device to modprobe a relevant module. As a result, you could have the module for your sound card load only when someone actually tries to access /dev/dsp.

This doesn't work with devfs. If the sound module isn't loaded, there is no /dev/dsp. There is no /dev/audio/whatever either. The kernel is not yet aware that there is a sound card in the machine. As far as I understood, that was the reason devfs is not on by default, nor is it even maintained any longer.

Muli said something about a replacement, but you will have to ask him about that.

--
Shachar Shemesh
Lingnu Open Source Consulting
http://www.lingnu.com/


================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]



Reply via email to