linux-kernel - Re: [PATCH] Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <1249575658.19886.8.camel@lap75545.ornl.gov>
Date:	Thu, 06 Aug 2009 12:20:58 -0400
From:	David Dillow <dave@...dillows.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	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>, gregkh@...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, 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? And for distros that want
to support that, does this really reduce the amount of code in the
initrd?
--
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/