On Mon, Jul 20, 2015 at 3:27 PM, Matthias G. Eckermann
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,
It's like saying what drive, what partition/volume, what directory is booted is also irrelevant. For most people as long as is just works, it's not immediately relevant. But for free and open source software in particular I think even when things are working it's also important that how they work, their discrete steps, can be followed and understood logically, are discoverable and self-describing as much as practical. This is a regression in that sense because it lacks all of those things.
But you care about the specific configuration (Date, kernel version, config status) you want to go back to. Don't you?
Sure. I also care about consistent domain of file system features. And this is a user domain feature, but it's been taken away by design for the exclusive use by a utility for just the boot volume. That's also confusing and non-obvious. The bigger issue here is that the way Linux OS's boot are diverging in increasingly incompatible ways. It's the opposite of standardization. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org