public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 09:19:10 -0700	[thread overview]
Message-ID: <3D5D25FE.8010002@us.ibm.com> (raw)
In-Reply-To: 20020816143925.GA3957@kroah.com

Greg KH wrote:
> All it takes is one line added to /etc/fstab mounting driverfs at /sys.
> As the code is not a .config option, you are using it if you mount it or
> not :)  The fact that no one else will look at that mount point,
> shouldn't matter to you.
> 
> And yes, for just one thing (hey, why don't you move _all_ the vm stats
> over to it), it is worth adding that one line.  And you'll eventually
> have to do it anyway, as these things _will_ be moving there.
> 
> Hell, tell me which machine you are using, and I'll go add it.

How long has it been in the tree (2.4 and 2.5)?  I'll add it to my 
machine, but I am anticipating a 3 hour conversation as I explain to 
the other users why they got dropped to a root prompt because driverfs 
isn't supported when they boot.

-- 
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2002-08-16 16:15 UTC|newest]

Thread overview: 11+ 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  8:51   ` Dave Hansen
2002-08-16 14:39     ` Greg KH
2002-08-16 16:19       ` Dave Hansen [this message]
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 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=3D5D25FE.8010002@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox