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: <ac3eb2510908061031t43691fb0k14f8bd2da49e991f@mail.gmail.com>
Date:	Thu, 6 Aug 2009 19:31:30 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Al Boldi <a1426z@...ab.com>
Cc:	Andi Kleen <andi@...stfloor.org>, Greg KH <greg@...ah.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.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, Aug 6, 2009 at 19:27, Al Boldi<a1426z@...ab.com> wrote:
> Kay Sievers wrote:
>> On Thu, Aug 6, 2009 at 19:06, Al Boldi<a1426z@...ab.com> wrote:
>> > 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.
>> >
>> > Oh good, I thought I was the only one doing that.
>> >
>> > The reason I don't like udev is that it's just to slow; something like a
>> > 5-10s delay on each boot.  No idea why it should be so slow,
>>
>> Because you setup is broken, I guess.
>>
>> > but it's probably
>> > probing the kernel for all available devices at boot, when it could be
>> > much quicker by probing for the device on access.
>>
>> It takes more like 0.5 - 0.7 seconds on a usual setup.
>
> I don't know about your setup, but all dists I used (fedora, mandriva, ubuntu,
> debian) hang every boot for 5-10s.

That's just not true. If you want to solve your issue, which has
nothing to do with devtmpfs, please move that to the
linux-hotplug@...r.kernel.org list.

Thanks,
Kay
--
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/