From: Goffredo Baroncelli <kreijack@inwind.it>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Naming of (bootable) subvolumes
Date: Sun, 28 Oct 2012 10:25:01 +0100 [thread overview]
Message-ID: <508CF9ED.5040806@inwind.it> (raw)
In-Reply-To: <52C8A7E3-239C-45C8-BB50-D66F4C2312D7@colorremedies.com>
On 2012-10-27 19:22, Chris Murphy wrote:
>
> On Oct 26, 2012, at 9:03 PM, Fajar A. Nugraha <list@fajar.net>
> wrote:
>
>>
>> So back to the original question, I'd suggest NOT to use either
>> send/receive or set-default. Instead, setup multiple boot
>> environment (e.g. old version, current version) and let user choose
>> which one to boot using a menu.
>
> Is it possible to make a functioning symbolic or hard link of a
> subvolume?
>
> I'm fine with "current" and "previous" options. More than that seems
> unnecessary. But then, how does the user choose? What's the UI? Is
> this properly the domain of GRUB2 or something else?
On my computer, when update-grub is called, it scans for all the
subvolumes and show them in the menu, allowing the user to switch at
boot time.
[...]
>
> Example. The following are all subvolumes, subvolume set-default 0,
> fstab uses subvol=home, subvol=root, subvol=boot for mount options.
>
> toplevel ├── boot ├── home ├── root ├── fedora18 │ ├── boot │ └──
> root
>
> On this system, grub-mkconfig produces a grub.cfg only for the system
> I'm currently booted from. It does not include any entries for
> fedora18/boot, fedora18/root, even though they are well within the
> normal search path. And the reference used is relative, i.e. the
> kernel parameter in the grub.cfg is rootflags=subvol=root
>
> If it were to create entries potentially for every snapshotted
> system, it would be a very messy grub.cfg indeed.
I don't think so. If a subvolume has a /sbin/int and and /etc it would
be suitable to be used as root filesystem.
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2012-10-28 9:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 12:30 Naming of subvolumes Richard Hughes
2012-10-25 13:18 ` anand jain
2012-10-25 13:28 ` Hugo Mills
2012-10-25 13:44 ` Richard Hughes
[not found] ` <CAAeznTr6AvqbJ+WOw6S5kyW2_qbSUQgJfAO88m9KdV+3PyGUcw@mail.gmail.com>
2012-10-25 15:16 ` Richard Hughes
2012-10-25 15:59 ` Calvin Walton
2012-10-25 17:19 ` Richard Hughes
2012-10-26 5:24 ` Chris Murphy
2012-10-26 8:27 ` Richard Hughes
2012-10-26 15:54 ` Chris Murphy
2012-10-27 1:58 ` cwillu
2012-10-27 3:03 ` Fajar A. Nugraha
2012-10-27 17:22 ` Naming of (bootable) subvolumes Chris Murphy
2012-10-28 9:25 ` Goffredo Baroncelli [this message]
2012-10-28 16:57 ` Chris Murphy
2012-10-28 9:38 ` Fajar A. Nugraha
2012-10-27 16:08 ` Naming of subvolumes Chris Murphy
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=508CF9ED.5040806@inwind.it \
--to=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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;
as well as URLs for NNTP newsgroup(s).