Richard Gooch wrote:
>> Devfs _is not_ the place for generic, driver-specific text output to
>> userspace.
>
> I don't agree. /proc should be for processes and *nothing* else.
Maybe, but right now it certainly isn't. Trying to migrate everything
to devfs is likely to leave you with half of the neither-process-nor-
device stuff in /proc and the rest in /devfs, leaving you with two
kitchen sinks. Please don't try to do this.
Besides, I don't quite understand all the fuss about /proc. It's not
overly hard to distinguish process and non-process entries (isdigit),
and I doubt that readdir'ing over the respective wrong kind is much of
a performance issue. So moving them elsewhere may at best create a lot
of forced upgrades (i.e. basically everything reading /proc also reads
non-process entries).
Some people argue that the non-process entries in /proc should
disappear entirely. I don't want to re-iterate this particular
discussion, just let me say that a large percentage of people putting
things into /proc disagree with this view :-) Also let me point out
that /proc entries are typically self-contained, which is a major
advantage for deployment.
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_N_032__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/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:32 EST