>>> Chris Murphy <[email protected]> schrieb am 28.12.2021 um 20:02 in Nachricht <CAJCQCtTfUWVP0NMGtTb7CM3bY6UCGnmNr+r0_L=z9tw5er-...@mail.gmail.com>: > On Mon, Dec 27, 2021 at 3:40 AM Ulrich Windl > <[email protected]> wrote: >> >> >>> Ludwig Nussel <[email protected]> schrieb am 21.12.2021 um 14:57 in >> Nachricht <[email protected]>: >> >> ... >> > The way btrfs is used in openSUSE is based on systems from ten years >> > ago. A lot has changed since then. Now with the idea to have /usr on a >> > separate read-only subvolume the current model doesn't really work very >> > well anymore IMO. So I think there's a window of opportunity to change >> > the way openSUSE does things :-) >> >> Oh well, while you are doing so: Also improve support for a separate /boot >> volume when snapshotting. > > Yeah how to handle /boot gives me headaches. We have a kind of > rollback, the possibility of choosing among kernels. But which kernels > are bootable depends on the /usr its paired with. We need a mechanism > to match /boot and /usr together, so that the user doesn't get stuck > choosing a kernel version for which the modules don't exist in an > older generation /usr. And then does this imply some additional > functionality in the bootloader to achieve it, or should this > information be fully encapsulated in Boot Loader Spec compliant > snippets?
Well, it's a bit off-topic, but: I had to use a separate /boot device due to the way my device is encrypted. Everything had seemed to work fine until I tried to install the AMD graphics driver that resulted in a failed boot (I can't remember the exact details). Unfortunately AFTER that I found out that there were no snapshots of /boot created (only of the root filesystem). (So recovery was a bit messy) Meanwhile I had enabled /boot snapshots also, but still no boot snapshots are offered in the GRUB menu... Basically that's what I had meant. Regards, Ulrich > > > -- > Chris Murphy
