From: David Woodhouse <dwmw2@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Anthony Roberts <btrfs-devel@arbitraryconstant.com>,
Linux btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: questions about GRUB and BTRFS
Date: Tue, 21 Apr 2009 16:13:52 +0100 [thread overview]
Message-ID: <1240326832.3632.46.camel@macbook.infradead.org> (raw)
In-Reply-To: <1235593343.32346.73.camel@think.oraclecorp.com>
On Wed, 2009-02-25 at 15:22 -0500, Chris Mason wrote:
> > This suggests another question for me... right now you can specify a root=
> > command line to the kernel, though there's other stuff like nfsroot= where
> > more parameters are needed. Is it possible to add a btrfsroot= option with
> > a UUID+subvolume?
>
> I'm not a huge fan of initrds, but the distro initrd scripts already
> have this kind of goodness hooked in. I think that's the best place for
> it.
Definitely. We're talking about _removing_ the nfsroot stuff that
Anthony refers to, in fact, on the basis that it can be done within an
initrd and doesn't have to live in the kernel.
Mount by UUID for other file systems is already handled by initrd; the
kernel can't do it for itself.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
prev parent reply other threads:[~2009-04-21 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:32 questions about GRUB and BTRFS Anthony Roberts
2009-02-25 1:53 ` Dmitri Nikulin
2009-02-25 6:03 ` Lee Trager
2009-02-25 18:19 ` Thomas Kuther
2009-02-25 18:22 ` Chris Mason
2009-02-25 20:04 ` Anthony Roberts
2009-02-25 20:22 ` Chris Mason
2009-04-21 15:13 ` David Woodhouse [this message]
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=1240326832.3632.46.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=btrfs-devel@arbitraryconstant.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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