From: Kay Sievers <kay.sievers@vrfy.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>, Arjan van de Ven <arjan@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default
Date: Sat, 16 Jan 2010 16:51:23 +0100 [thread overview]
Message-ID: <ac3eb2511001160751g2357bf2en2bfacaabe5c2f7e@mail.gmail.com> (raw)
In-Reply-To: <20100115205722.3580b6bf@lxorguk.ukuu.org.uk>
On Fri, Jan 15, 2010 at 21:57, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> Why? All major distros need this at boot time, and as we have been
>
> No they don't.
>
> Centos doesn't (in fact I suspect it'll break)
> Fedora 11 doesn't
> Fedora 12 doesn't seem to (but seems to be willing to use it)
> Ditto all the older SuSE, Ubuntu etc releases that are *still*
> active/supported/maintained
Fedora, SUSE, Ubuntu, ... All releases currently in development enable
and use it.
>> through a release cycle with the config option, anyone who is
>> incrementally updating will continue with their existing value. But new
>> people coming in, will get the option as it is most likely required to
>> boot properly.
>>
>> Makes sense to me.
>
> That may well be true - in which case it needs to be very clearly
> documented when to enable it.
For now, the systems will bootup fine without it, but I expect over
time, it will get a requirement. Udev does not care about it, but the
boot scripts/initramfs tools will probably get trimmed down, because
there is much less to do with the kernel provided nodes, than what is
needed today to bootstrap /dev.
And it should not harm any old system if it is enabled. If initramfs
is used it's completely invisible, if a custom kernel with
kernel-mounted rootfs is used, the udev boot script usually
over-mounts the devtmpfs at /dev with an empty tmpfs, like it has
always done it before.
The only thing it should change is that we now should be able to
bootup a box without an initramfs, without manually filling /dev with
static nodes beforehand. Current distro installations do not put a
single file in /dev on the rootfs, and trying to boot a kernel without
an initramfs usually just fails without putting some nodes there in
preparation.
Thanks,
Kay
next prev parent reply other threads:[~2010-01-16 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 21:47 Kay Sievers
2010-01-15 14:08 ` Stefan Richter
2010-01-15 18:02 ` Greg KH
2010-01-15 14:56 ` Arjan van de Ven
2010-01-15 18:03 ` Greg KH
2010-01-15 20:57 ` Alan Cox
2010-01-16 15:51 ` Kay Sievers [this message]
2010-01-16 16:27 ` Alan Cox
2010-01-16 20:11 ` Arjan van de Ven
2010-01-17 7:56 ` Pavel Machek
2010-01-17 14:58 ` Arjan van de Ven
2010-01-20 17:53 ` Kay Sievers
2010-01-21 6:05 ` Arjan van de Ven
2010-01-21 16:37 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac3eb2511001160751g2357bf2en2bfacaabe5c2f7e@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®