Messages in this thread | | | From | (david parsons) | Subject | Re: devfs again, (was RE: USB device allocation) | Date | 6 Oct 1999 11:49:54 -0700 |
| |
In article <linux.kernel.199910061701.NAA22845@pincoya.inf.utfsm.cl>, Horst von Brand <vonbrand@inf.utfsm.cl> wrote: >"Jakma, Paul" <Paul.Jakma@compaq.com> said: > >[...] > >> - devfs does not implement policy. >> >> The actual device names are not decided by devfs, and neither are >> permissions. >> >> Device names are decided by the driver registering them. [...] > >Names _are_ policy. So now I have to hack the kernel to rename the mouse?
That's what G-d invented symbolic links for.
The kernel exports policy no matter what; currently it exports policy via major and minor numbers, which someone has to root through source code and/or documentation to find and then link your namespace to, and with devfs it exports policy via a bunch of names that you can link your namespace to.
The _one_ difference between the two schemes is where permissions and ownership are applied; with block and character devices, you apply ownership and permissions to the link, and with symbolic links you apply ownership and permissions to the file.
____ david parsons \bi/ and with the devfsd hack, you get your ownership \/ persistance via the much-loved userspace bloat.
- 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/
| |