On Monday November 19, adilger@turbolabs.com wrote:
> On Nov 19, 2001 14:47 +1100, Neil Brown wrote:
> > - devfs puts a lot of miscellaneous stuff in the top level.
> > I would want to group them into one namespace. e.g.:
> > misc/memory/mem
> > misc/memory/kmem
> > misc/memory/zero
> > misc/memory/null
> > misc/random/random
> > misc/random/urandom
>
> Erm, what about the millions+ of scripts/apps that reference /dev/zero
> or /dev/null?
# ln -s misc/memory/null /dev/null
# mknod /dev/null c 0 0
I was talking about how naming should look inside the kernel. The
names that are presented to user-space are up to user-space. The
names that are used internally should make sense internally.
mknod is there to provide a gateway between the two.
Devfs defines internal names which are, to some extent, chosen to
match expected external names. This is putting policy in the kernel,
which is one of the complaints about devfs.
Devfs actually has a bit each way. There is a concept of "compatible"
names which are imposed on devfs by devfsd, so that internal names
don't have to match external names. But many interal names do still
match historical external names.
I would like a very well defined and rigidly adhered to structure for
internal names. This should be chosen to match the internal (actual
or planned) of the kernel. And there should be a mechanism to allow
user-space to define external names to map to those internal names.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 23 2001 - 21:00:19 EST