All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: snogglethorpe@gmail.com, miles@gnu.org
Cc: Greg KH <greg@kroah.com>, Mike Bell <kernel@mikebell.org>,
	Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.12-git
Date: Thu, 23 Jun 2005 00:03:09 -0700	[thread overview]
Message-ID: <20050623070309.GA12158@suse.de> (raw)
In-Reply-To: <fc339e4a05062223365c2a5ed5@mail.gmail.com>

On Thu, Jun 23, 2005 at 03:36:11PM +0900, Miles Bader wrote:
> On 6/23/05, Greg KH <greg@kroah.com> wrote:
> > Not that I know of.  If you want to do this, compare the original udev
> > releases that were around 5kb of code, as the nice features it has today
> > are stuff that devfs can not support at all.
> 
> That wouldn't be such an effective tool for convincing people to
> switch though... :-)  "Look this obsolete version is much smaller!"
> 
> If udev has really bloated up due to whizzy new features, how hard
> would it be to compile a stripped-down version?  [Well I should look
> at the busybox support somebody mentioned -- perhaps it's exactly
> that.]

It wouldn't be that hard at all, just look at the first couple of
releases for example code to use (you would want it to be a totally
separate project, the current udev is not ment for such a stripped down
thing, it's ment to take over all of the /sbin/hotplug funcionality,
through netlink no less.)

thanks,

greg k-h

  reply	other threads:[~2005-06-23  8:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  6:29 [GIT PATCH] Remove devfs from 2.6.12-git Greg KH
2005-06-21  6:30 ` [PATCH] devfs: Remove devfs from the partition code Greg KH
2005-06-21  6:54 ` [GIT PATCH] Remove devfs from 2.6.12-git Andrew Morton
2005-06-21 13:50   ` Adrian Bunk
2005-06-21 15:10   ` Greg KH
2005-06-21 20:11     ` Andrew Morton
2005-06-21 20:52       ` Arjan van de Ven
2005-06-21 21:03         ` Andrew Morton
2005-06-21 21:16           ` Greg KH
2005-06-21 21:58             ` J.A. Magallon
2005-06-23  1:00     ` Mike Bell
2005-06-23  1:18       ` Andrew Morton
2005-06-23  2:13         ` Bill Gatliff
2005-06-23  4:59       ` Greg KH
2005-06-23  6:14         ` Miles Bader
2005-06-23  6:26           ` Greg KH
2005-06-23  6:36             ` Miles Bader
2005-06-23  7:03               ` Greg KH [this message]
2005-06-23 19:54             ` Kay Sievers
2005-06-23  6:34           ` Mike Bell
2005-06-23  6:37             ` Andrew Morton
2005-06-23  6:47               ` Mike Bell
2005-06-23  6:51               ` Greg KH
2005-06-23  6:38             ` Miles Bader
2005-06-23  6:28         ` Mike Bell
2005-06-23  6:48           ` Greg KH
2005-06-23  8:29             ` Mike Bell
2005-06-23 12:58               ` Theodore Ts'o
2005-06-24  8:24               ` Greg KH
2005-06-23 15:13             ` Per Liden
2005-07-18 16:36         ` Richard Gooch
2005-07-18 20:12           ` Jan Engelhardt
2005-07-18 22:29             ` Daniel Phillips
2005-07-19  2:51             ` Jim Crilly
2005-06-21 17:35 ` Carsten Otte
  -- strict thread matches above, loose matches on Subject: below --
2005-06-23  4:08 David Brownell
2005-06-23  6:21 ` Miles Bader
2005-06-23  8:10 ` Russell King
2005-06-23  5:08 David Brownell
2005-06-23  5:22 ` Bill Gatliff

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=20050623070309.GA12158@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=kernel@mikebell.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    --cc=snogglethorpe@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.