From: Anthony Roberts <btrfs-devel@arbitraryconstant.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linux btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: questions about GRUB and BTRFS
Date: Wed, 25 Feb 2009 13:04:42 -0700 [thread overview]
Message-ID: <6e246ee64cdb6decfd7153436888efcb@smtp.arbitraryconstant.com> (raw)
In-Reply-To: <1235586140.32346.37.camel@think.oraclecorp.com>
Hi Chris,
Cheers for the informative response. :)
> In the ideal implementation, the grub.conf has a list of devices it is
> allowed to scan, and we put the FS uuid directly in there, let grub scan
> them and we'll be able to boot off multiple volumes in that way.
Hm... perhaps it doesn't even need that much. It we're specifying devices,
might it simply pull the UUID out of the initial device it's given, kinda
like how the current mounting process works? Enumeration of the drives
changes as they come and go, but it doesn't really matter what "hd0" is
today as long as it's a member device.
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?
With these features exposed to the booting process, it seems like there are
a *lot* of very powerful use cases that become possible with management of
the OS itself.
> But, that is a significant project, so we'll have to do it in stages.
Indeed. It's not my expectation it be done initially or even soon, just my
hope that it "eventually" become as flexible in booting as it is once the
system goes multi-user. :)
-Anthony
next prev parent reply other threads:[~2009-02-25 20:04 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 [this message]
2009-02-25 20:22 ` Chris Mason
2009-04-21 15:13 ` David Woodhouse
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=6e246ee64cdb6decfd7153436888efcb@smtp.arbitraryconstant.com \
--to=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