https://bugzilla.redhat.com/show_bug.cgi?id=1576413 --- Comment #15 from Neal Gompa <ngompa13@xxxxxxxxx> --- (In reply to Marian Csontos from comment #9) > I think snpshots of /boot has its own set of problems. One of snapper's > flaws when using BTRFS is exactly that - it keeps information about > snapshots inside the filesystem which is "snapshotted". > I wouldn't be snapshotting /boot at the same time as / if it weren't for the fact that we deliberately install crap there. The reason I do it is because everything from EFI files (shim and grub2), GRUB module files, to kernel images, to stuff like this is being installed there, and the rpmdb isn't happy when those files are "mysteriously missing" or "wrong". > I wonder, if you have multiple snapshots of /boot, where do you keep > information about those snapshots and grub.cfg to pick the > snapshot+kernel+initrd+cmdline to boot? > You're right that this is a problem. I currently have the information on ESP, but I don't like it there. It'd be cleaner if stuff wasn't getting installed into /boot directly and everything in there was something that was recoverable from the main filesystem. Then I could leave /boot alone. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
