From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove compat code for old devfs naming scheme
Date: Tue, 14 May 2002 09:47:37 -0600 [thread overview]
Message-ID: <200205141547.g4EFlbR09184@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20020514163347.A5474@infradead.org>
Christoph Hellwig writes:
> On Tue, May 14, 2002 at 08:59:41AM -0600, Richard Gooch wrote:
> > The reason to support it is because lots of people are depending on
> > it. A lot of systems would break for no real gain. This code is in the
> > init section, so the memory will be freed before init(8) starts.
> >
> > The code should stay. In 2.5, I can move it into the mini devfsd that
> > will go into the initial rootfs.
>
> Exactly how many system exist which
>
> a) still use the two or three year old devfs naming scheme for
> their root= command line
> b) use current 2.5 kernels
Those names are not really "old", but convenient shorthand. And it's
more systems than you think.
> and
>
> c) have users not capable of translating that syntax to either
> the new devfs or traditional Linux syntax?
>
> I don't think there are more then about ten, and no I _absolutely_
> do not consider that a reason to bloat the kernel, even if it is just
> source and image bloat.
A lot more people are using devfs than you realise. Removing the code
would screw them over. Leave it alone.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
prev parent reply other threads:[~2002-05-14 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 11:53 Christoph Hellwig
2002-05-14 14:35 ` Richard Gooch
2002-05-14 14:55 ` Christoph Hellwig
2002-05-14 14:59 ` Richard Gooch
2002-05-14 15:33 ` Christoph Hellwig
2002-05-14 15:47 ` Richard Gooch [this message]
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=200205141547.g4EFlbR09184@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=hch@infradead.org \
--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
all inboxes | Powered by JetHome®