Greg KH wrote:
> On Thu, Aug 15, 2002 at 07:31:44PM -0700, Dave Hansen wrote:
>
>> Not _another_ proc entry!
>
> Yes, not another one. Why not move these to driverfs, where they
> belong.
Could you show us how this particular situation might be laid out in a
driverfs/kfs/gregfs tree?
It's great that you keep suggesting this, but we have another
chicken-and-egg problem.
<SOAPBOX>
The problem with driverfs today is that it isn't worth it for _me_ to
use it to just get this one, single thing. If I used driverfs right
now, the only thing that I would get out of it would be ... buddyinfo!
How is it worth my while to use it on a shared machine where most
people probably won't be mounting driverfs, or _want_ it mounted as
the default?
</SOAPBOX>
> (ignore the driverfs name, it should be called kfs, or some such
> thing, as stuff more than driver info should go there, just like
> these entries.)
If even its most ardent supporters don't like its name...
-- Dave Hansen haveblue@us.ibm.com- 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 Aug 23 2002 - 22:00:11 EST