Me wonders: why do you care about the specific subvolume,
which the system is booting from?
That information is "irrelevant" in the sence
that if you roll back you don't care about btrfs or subvolumes,
But you care about the specific configuration
(Date, kernel version, config status)
you want to go back to.
Don't you?
MgE
Am 20. Juli 2015 21:26:56 MESZ, schrieb Chris Murphy
On Mon, Jul 20, 2015 at 12:20 PM, Chris Murphy
wrote: Yes it's esoteric, yes it's hidden.
More examples of this:
- posting grub prefix, grub.cfg, dmesg or journal, no one can have any idea what root the system actually boots from. This is unlike non-Btrfs installations.
- from GRUB, editing the grub menu, I have no way to determine what subvolume will be booted.
- from GRUB CLI, I can't determine what the default subvolume is, even if I have the esoteric knowledge that is subvolumes and subvolume ID and the concept of default subvolumes.
There's no way to know what subvolume was or will be booted, unless you have a working Linux installation with btrfs-progs in order to a.) mount the btrfs volume, and then b.) btrfs sub get-default.
It's so esoteric and hidden I can't imagine on what basis someone could describe it as being obvious and found in plain sight.
-- Sent from my mobile phone. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org