From: Eric Valette <eric.valette@free.fr>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Phil Turmel <philip@turmel.org>,
linux-kernel@vger.kernel.org,
Florian Mickler <florian@mickler.org>
Subject: Re: Please add generic support for root=UUID= at kernel parameter command line (LABEL, BYID maybe also)
Date: Fri, 27 Aug 2010 21:09:06 +0200 [thread overview]
Message-ID: <4C780D52.4080108@free.fr> (raw)
In-Reply-To: <20100827163753.GA13252@citd.de>
On 27/08/2010 18:37, Matthias Schniedermeyer wrote:
> I don't really get what you mean.
> But binary duplication isn't the issue, source-code duplication is.
> I'd count an initramfs to the binary category. It is "compiled" more or
> less literaly.
binary duplication is a waste of space (SSD are'nt cheap) and time.
Plus, you have a real duplication for the fs-search in grub/lilo/add
your favorite evolved boot loader there.
>> 3) The tmpdevfs is also a dupplicate somehow
>
> No.
>
> devtmpfs uses tmpfs or ramfs as backing-store. And it doesn't really
> duplicate udev either, as it only does the bare minimum needed to get
> the computer to the point where udev can do the rest. Like when you have
> a root filesystem with no /dev at all.
I know. But It could do just a bit more find creating the
/dev/disk/by-uuid/foo where foo is the one given ib root=UUID=foo
--eric
next prev parent reply other threads:[~2010-08-27 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 14:37 Please add generic support for root=UUID= at kernel parameter command line (LABEL, BYID maybe also) Eric Valette
2010-08-23 21:56 ` Phil Turmel
2010-08-26 15:32 ` Eric Valette
2010-08-26 19:53 ` Phil Turmel
2010-08-27 11:59 ` Eric Valette
2010-08-27 16:37 ` Matthias Schniedermeyer
2010-08-27 19:09 ` Eric Valette [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-23 14:10 Eric Valette
2010-08-23 20:05 ` Florian Mickler
2010-08-23 20:11 ` H. Peter Anvin
2010-08-24 10:06 ` Florian Mickler
2010-08-24 8:19 ` Eric Valette
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=4C780D52.4080108@free.fr \
--to=eric.valette@free.fr \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
--cc=philip@turmel.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