Bigger "dev_t"s
Guy Harris
guy at auspex.UUCP
Sat Nov 12 15:45:13 AEST 1988
>Better yet, have /dev be a special file system of its own (using the
>file system switch) that takes care of the details of mapping strings
>to driver entries.
One nuisance with this would be that, unless the contents of this file
system were somehow recorded (completely or partially) in some form of
non-volatile storage, you'd have to stick bunches of "chown" commands in
some place such as "/etc/rc" in order to be able to administer
permissions on files. The simplest implementation of such a file system
would give all "/dev" files the same permissions, and that would either
be too restrictive or too permissive a default; fancier implementations
would quite likely put policy code into the kernel, which I would oppose
both for philosophical and practical reasons.
I don't have any great problem with the "chown"s being stuck in
"/etc/rc" (the moral equivalent of those "chown"s are in "/dev/MAKEDEV"
on BSD systems and systems that have adopted MAKEDEV from BSD, for
example), but it may be a minor inconvenience to have to stick them there.
More information about the Comp.unix.wizards
mailing list