From: Dave Hansen <haveblue@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Subject: Re: [PATCH] add buddyinfo /proc entry
Date: Fri, 16 Aug 2002 01:51:08 -0700 [thread overview]
Message-ID: <3D5CBCFC.2090006@us.ibm.com> (raw)
In-Reply-To: 20020816043140.GA2478@kroah.com
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
next prev parent reply other threads:[~2002-08-16 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 2:31 [PATCH] add buddyinfo /proc entry Dave Hansen
2002-08-16 4:31 ` Greg KH
2002-08-16 4:31 ` Greg KH
2002-08-16 8:51 ` Dave Hansen [this message]
2002-08-16 14:39 ` Greg KH
2002-08-16 16:19 ` Dave Hansen
2002-08-16 16:37 ` Greg KH
2002-08-16 19:03 ` Patrick Mochel
2002-08-16 21:04 ` Dave Hansen
2002-08-19 0:04 ` Rusty Russell
2002-08-16 14:31 ` Andrew Morton
2002-08-16 14:31 ` Andrew Morton
2002-08-16 21:03 ` William Lee Irwin III
2002-08-16 21:03 ` William Lee Irwin III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D5CBCFC.2090006@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.