Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default
in [Kernel]
|
Prev: [PATCH] cxgb3: fix hot plug removal crash
Next: [PATCH] pid_ns: zap_pid_ns_processes: use SEND_SIG_NOINFO instead of force_sig()
From: Kay Sievers on 3 Mar 2010 15:10 On Wed, Mar 3, 2010 at 06:46, Linus Torvalds <torvalds(a)linux-foundation.org> wrote: > Greg, please shut down people like Kay that want to enable something by > default. We want a _minimal_ working config, not a maximal. If somebody > has a distro that needs this, they can enable it _then_. Not "let's try to > make people enable it whether they need it or not, because they _might_". > > Because "might need it" is simply not good enough. A "must have" is the > only reason to do 'default y'. No problem, if that's he rule, then let's drop the "y". I always understood the defaults as the "usually needed to bring up a box" setting. We had this discussion already with Arjan who stated the same as you, but we kid of missed to take action on that, sorry. 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. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Kay Sievers on 3 Mar 2010 17:10
On Wed, Mar 3, 2010 at 10:21, Eric W. Biederman <ebiederm(a)xmission.com> wrote: > Kay Sievers <kay.sievers(a)vrfy.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(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |