mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Greg KH <greg@kroah.com>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	hch@infradead.org
Subject: Re: [BK PATCH] minor devfs cleanup for 2.5.40
Date: Fri, 4 Oct 2002 17:24:57 +0100	[thread overview]
Message-ID: <20021004172457.A3390@infradead.org> (raw)
In-Reply-To: <200210041617.g94GHY008334@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Fri, Oct 04, 2002 at 10:17:34AM -0600

On Fri, Oct 04, 2002 at 10:17:34AM -0600, Richard Gooch wrote:
> Greg KH writes:
> > Here's a changeset from Christoph Hellwig that removes some unneeded
> > code from the kernel core.  This was leftover from before devfs became
> > part of the main kernel tree, and was trying to do some naming fixups in
> > kernelspace.  If anyone still has machines using these names, their
> > startup scripts should be modified to use the "standard" devfs names.
> > 
> > Please pull from:  http://linuxusb.bkbits.net/devfs-2.5
> 
> NO! Dammit, you'll break everyone who is using these compact names to
> mount the root FS. Look more closely at the code you're trying to
> remove, and you'll see it's *not* used to avoid work in startup
> scripts. It's only used to create the devfs entry for the root FS.

This is 2.5 and those names were never in mainline.  Use your new
devfs names or plain linux names or just hex numbers.  Linux is
not a place were we keep junk around.


  reply	other threads:[~2002-10-04 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 21:39 Greg KH
2002-10-03 21:40 ` Greg KH
2002-10-04 16:17 ` Richard Gooch
2002-10-04 16:24   ` Christoph Hellwig [this message]
2002-10-04 16:27     ` Richard Gooch
2002-10-04 16:31       ` Christoph Hellwig
2002-10-04 16:37         ` Richard Gooch

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=20021004172457.A3390@infradead.org \
    --to=hch@infradead.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --cc=torvalds@transmeta.com \
    /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®