public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devfs: remove devfs from Kconfig preventing it from being built
Date: Tue, 21 Jun 2005 21:13:30 -0700	[thread overview]
Message-ID: <20050622041330.GB27716@suse.de> (raw)
In-Reply-To: <20050621.155919.85409752.davem@davemloft.net>

On Tue, Jun 21, 2005 at 03:59:19PM -0700, David S. Miller wrote:
> From: Greg KH <gregkh@suse.de>
> Date: Tue, 21 Jun 2005 15:24:19 -0700
> 
> > Here's a much smaller patch to simply disable devfs from the build.  If
> > this goes well, and there are no complaints for a few weeks, I'll resend
> > my big "devfs-die-die-die" series of patches that rip the whole thing
> > out of the kernel tree.
> > 
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> 
> I know the rational behind this.
> 
> However, this does mean I do need to reinstall a couple
> debian boxes here to something newer before I can continue
> doing kernel work in 2.6.x on them.

Those boxes rely on devfs?

Can't you just grab the "static dev" debian package and continue on?
I'm sure there is one in there somewhere (don't really know for sure,
not running debian anywhere here, sorry.)

Or how about a tarball of a /dev tree?  Would that help you out?

thanks,

greg k-h

  reply	other threads:[~2005-06-22  4:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 22:24 [PATCH] devfs: remove devfs from Kconfig preventing it from being built Greg KH
2005-06-21 22:59 ` David S. Miller
2005-06-22  4:13   ` Greg KH [this message]
2005-06-22  4:45     ` David S. Miller
2005-06-22  6:23       ` Coywolf Qi Hunt
2005-06-22  8:37         ` J.A. Magallon
2005-06-22  9:23           ` Coywolf Qi Hunt
2005-06-22  6:40       ` Martin J. Bligh
2005-06-23  3:45         ` Jim Crilly
2005-06-23 10:02       ` Helge Hafting
2005-06-22  8:22   ` Christoph Hellwig
2005-06-22 15:34     ` Nix

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=20050622041330.GB27716@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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