Alexander Viro wrote:
> They are different code-wise and ought to be separated. As soon as we'll
> have working unionfs (or at least non-opaque mount) they *will* be
> separated.
And what problem would this solve, besides a slight aesthetical discomfort
some may perceive ? procfs exports a fairly generic VFS interface, so it's
easy to attach subtrees with whatever semantics you like. Gluing /proc
together from various components, possibly with their own sets of support
functions, just seems like a good way to waste resources and to
de-stabilize the name space (top --pids-are-here=/kernel/pids \
--uptime-is-here=/kernel/misc --meminfo-is-here=/kernel/vm ? ;-)
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_R_131__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/- 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/