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]
Date:	Wed, 3 Mar 2010 12:01:31 -1000
From:	Kay Sievers <kay.sievers@...y.org>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 19/62] Driver-Core: devtmpfs - remove EXPERIMENTAL and 
	enable it by default

On Wed, Mar 3, 2010 at 10:21, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> Kay Sievers <kay.sievers@...y.org> writes:
>> For the "must have", we will not be able to bootup the upcoming Ubuntu
>> and openSUSE development distros without it, not sure about Fedora,
>> the support is there, but it might still work without it. Some smaller
>> distros also already depend on it.
>
> Is this a case of the initial ramdisks won't work, or have you removed
> support from udev to create device nodes?

Udev has not changed, it still works without any kernel-created nodes,
as it always did.

It's the distro-specific system coldplug/bootstrap logic that got
simplified with the kernel device-node support. There is more pending,
which will take the advantage of not needing to synchronize some
steps, like it was needed the former asynchronous device-node-creation
behavior. It affects initramfs and kernel-mounted rootfs setups, both
now expect devtmpfs to be available.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ