Yes, you are missing something here. The entire point is that devfs is
not getting into the kernel in its current form. There has been really
strong opposition from some very high-ranking kernel developers. It is
pointless to continue the argument using the existing devfs. It simply
is Not Going To Happen. There's no point fighting that.
This is why I suggested losing the devfs FILESYSTEM but retaining what
is devfs's INTENTION. Use the existing devfsd to maintain nodes on the
disk. Most of the benefits are kept. Some problems are addressed.
> > - You can just turn off the daemon, old behaviour is restored.
>
> No, it is not.. You can unmount devfs, and it will be restored, however.
You're still missing something. The post you responded to doesn't talk
about a filesystem called devfs at all. The very first sentence of the
post you responded to made this explicitly clear.
--
Nathan Hand - Chirp Web Design - http://www.chirp.com.au/ - $e^{i\pi}+1 = 0$
Phone: +61 2 6230 1871 Fax: +61 2 6230 1515 E-mail: nathanh@chirp.com.au
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/