[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1250081813.26788.13.camel@obelisk.thedillows.org>
Date: Wed, 12 Aug 2009 08:56:53 -0400
From: David Dillow <dave@...dillows.org>
To: Greg KH <greg@...ah.com>
Cc: Andi Kleen <andi@...stfloor.org>, Greg KH <gregkh@...e.de>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>,
Jan Blunck <jblunck@...e.de>, Harald Hoyer <harald@...hat.com>,
Scott James Remnant <scott@...ntu.com>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] Driver Core: devtmpfs - kernel-maintained tmpfs-based
/dev
On Tue, 2009-08-11 at 17:34 -0700, Greg KH wrote:
> On Tue, Aug 11, 2009 at 08:25:27PM -0400, David Dillow wrote:
> > So use Eric/Arjan's program that does it in 60ms -- you get a
> > dynamic /dev, no initrd, fast boot, and no kernel changes required.
>
> Their program only handles it for a reconstruction of /dev based on
> sysfs one time at boot. It does not handle things that are added or
> discovered by the system after that, you need udev for that.
>
> So it's a great hack for boot time stuff, but not a complete /dev
> management replacement like this code can be for numerous systems.
What systems would those be? Perhaps it's just too early in the morning
for me, but I'm having a hard time thinking of ones that wouldn't want
to use udev in that case for the event notification, or have their own
handler, such as an embedded system.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists