From: Gene Czarcinski <gene@czarc.net>
To: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: /boot as a btrfs subvolume
Date: Sun, 06 Jan 2013 15:05:29 -0500 [thread overview]
Message-ID: <50E9D909.1020207@czarc.net> (raw)
In-Reply-To: <50E9CDB3.3010401@petaramesh.org>
On 01/06/2013 02:17 PM, Swâmi Petaramesh wrote:
> Le 06/01/2013 20:11, Chris Murphy a écrit :
>> If you use UUID, and you use subvol=, and you don't rename/move your subvolume, it's perfectly safe. Nevertheless, GRUB becoming subvolid aware seems like a good idea to me, but I have no idea what's involved in that.
> I actually run several machines on which I have /boot in a separate
> BTRFS subvol, without any issue. I have a multiboot between several
> different distros (typically Ubuntu, Mint, LMDE, Bodhi... All Ubuntu
> derivatives except for LMDE which is Debian-based...) sharing the same
> BTRFS container and using different subvols i.e. UBUNTU/@boot,
> LMDE/@boot etc...
>
> Works just great.
>
I assume you have a "grub partition" (or its equivalent) with a grub.cfg
file having menuentry definitions [pointing to the different grub.cfg
file for each system ... that seems to work well (at least for me).
Currently, os-prober does not support btrfs.
I have taken a little look at the grub2 source code and there is some
mention of both btrfs and zfs (and also btrfs subvolumes) in the
changelogs. However, it is not clear to me (and I have not had the time
yet) to explore exactly what the source code is doing or not doing.
Gene
next prev parent reply other threads:[~2013-01-06 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 21:17 /boot as a btrfs subvolume Gene Czarcinski
2013-01-05 21:27 ` Chris Murphy
2013-01-06 14:44 ` Gene Czarcinski
2013-01-06 19:11 ` Chris Murphy
2013-01-06 19:17 ` Swâmi Petaramesh
2013-01-06 20:05 ` Gene Czarcinski [this message]
2013-01-07 2:00 ` Chris Murphy
2013-01-07 15:42 ` Gene Czarcinski
2013-01-07 18:42 ` Chris Murphy
2013-01-07 21:41 ` Gene Czarcinski
2013-01-07 22:04 ` Chris Murphy
2013-01-07 17:48 ` Swâmi Petaramesh
2013-01-07 19:28 ` Chris Murphy
2013-01-05 21:32 ` Chris Murphy
2013-01-06 14:37 ` Gene Czarcinski
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=50E9D909.1020207@czarc.net \
--to=gene@czarc.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.