From: Dave Hansen <haveblue@us.ibm.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Greg KH <greg@kroah.com>,
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 14:04:04 -0700 [thread overview]
Message-ID: <3D5D68C4.8030806@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0208161158270.1048-100000@cherise.pdx.osdl.net
Patrick Mochel wrote:
> You're making things up and spreading FUD. Why would you want to do that?
Because IBM has a grand, secret plan to replace driverfs with
BigBlueFS. We have brainwashed Linus into taking it and we will rule
the world!
No, I'm just being selfish and I'm a bit uninformed. I understand it
better now because Greg explained why you want to do it. The thing
that did it for me was Linus's decree that vm tunables _will_ move to
driverfs. That changes the scenario from "Greg and Patrick are
bitching" to "Linus wants this" and thus it will be the wave of the
future. Maybe you guys need to make this a bit more clear.
> Oh right, it's because most "kernel developers" would rather bitch about
> that which they do not understand and cut down other developers than suck
> it up and actually try to learn something from someone else.
I'm trying to understand, that's why I asked so many questions. I am
mistaken about the machine not booting completely if it doesn't
understand a fs-type, Greg corrected me here.
Summary:
A driverfs version of this patch is on the way.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-08-16 21:00 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
2002-08-16 16:37 ` Greg KH
2002-08-16 19:03 ` Patrick Mochel
2002-08-16 21:04 ` Dave Hansen [this message]
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=3D5D68C4.8030806@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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