public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [GIT PATCH] Remove devfs from 2.6.16
Date: Tue, 21 Mar 2006 00:58:46 +0100	[thread overview]
Message-ID: <20060320235846.GA84147@dspnet.fr.eu.org> (raw)
In-Reply-To: <20060320212338.GA11571@kroah.com>

On Mon, Mar 20, 2006 at 01:23:38PM -0800, Greg KH wrote:
> They are the same "delete devfs" patches that I submitted for 2.6.12 and
> 2.6.13 and 2.6.14 and 2.6.15.  It rips out all of devfs from the kernel
> and ends up saving a lot of space.  Since 2.6.13 came out, I have seen
> no complaints about the fact that devfs was not able to be enabled
> anymore, and in fact, a lot of different subsystems have already been
> deleting devfs support for a while now, with apparently no complaints
> (due to the lack of users.)

I'm an occasional user.  I'm just able to add a config entry by hand.

Devfs for block devices is required for the fedora core 3 install
kernel.  I haven't checked whether fc4 needs it too (DaveJ?), but if
it is the case it would be a real bad idea to remove it before fc6 is
out.

I know, I know, compatibility is for the weak.

  OG.


  parent reply	other threads:[~2006-03-20 23:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 21:23 [GIT PATCH] Remove devfs from 2.6.16 Greg KH
2006-03-20 21:32 ` Randy.Dunlap
2006-03-20 21:34   ` H. Peter Anvin
2006-03-20 21:40     ` Randy.Dunlap
2006-03-20 22:02   ` Greg KH
2006-03-20 23:58 ` Olivier Galibert [this message]
2006-03-21  0:05   ` Dave Jones
2006-03-21  7:15   ` Arjan van de Ven
2006-03-21 12:47     ` Olivier Galibert
2006-03-23  3:33 ` Kalin KOZHUHAROV
2006-03-23 21:29   ` Adrian Bunk
2006-03-28 22:30     ` Bill Davidsen

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=20060320235846.GA84147@dspnet.fr.eu.org \
    --to=galibert@pobox.com \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --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