[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090806183147.GA28409@suse.de>
Date: Thu, 6 Aug 2009 11:31:47 -0700
From: Greg KH <gregkh@...e.de>
To: David Dillow <dave@...dillows.org>
Cc: Andi Kleen <andi@...stfloor.org>, Greg KH <greg@...ah.com>,
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>
Subject: Re: [PATCH] Driver Core: devtmpfs - kernel-maintained tmpfs-based
/dev
On Thu, Aug 06, 2009 at 12:20:58PM -0400, David Dillow wrote:
> On Thu, 2009-08-06 at 17:46 +0200, Andi Kleen wrote:
> > Greg KH <greg@...ah.com> writes:
> > >
> > > It makes the userspace boot process much simpler and easier to maintain,
> > > as well as providing a way to handle rescue disks and images trivially,
> > > and it makes the kernel _less_ dependant on the early userspace bootup
> > > scripts.
> >
> > As a initrd less kernel user I can really only agree: getting rid
> > of the udev-in-initrd requirement would be a big step forward
> > in usability. Typically I always have to pre populate
> > a on disk /dev manually first to get my kernels to boot.
>
> If you use mount by label or UUID, you still need udev (or other tools)
> in the initrd to find the right disk, correct?
Yes, you would.
> And for distros that want to support that, does this really reduce the
> amount of code in the initrd?
Yes it does, see the code in the Novell Moblin images for an example of
how to use devtmpfs with udev for how to do this.
thanks,
greg k-h
--
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