Why mount devfs on /devices instead of /dev?
The devfs file system is too useful to discard, yet too problematic to mount on top of /dev even with devfsd running. Devfs does not support autoloading modules in the same fashion that /dev does. /dev autoloading modules cease to automatically load. Additionally, one can not preserve the permissions and ownership for devices that are not loaded into the kernel, either directly compiled in or loaded as modules. A program can not probe a device, on the devfs file system, which is not there and have it’s module load. Consequently, as the devfs is a useful and intuitive filesystem for devices it should be kept and used in conjunction with /dev instead of as a replacement. That is why the devfs filesystem is mounted on /devices in Sorcerer.
