![](https://seccdn.libravatar.org/avatar/f9fb86af86ef66b34b610f49ebc61f39.jpg?s=120&d=mm&r=g)
Olaf Hering wrote:
Am Mon, 12 Apr 2021 10:46:48 +0200 schrieb Ludwig Nussel <ludwig.nussel@suse.de>:
One of the motivations for UsrMerge is to have all read-only parts of the operating system in /usr. The kernel packages install files in /boot though which isn't in line with that idea.
Meanwhile I think all the files below /boot are part of the same state that is supposed to be within the single to-be-snapshotted subvolume. As such the entire directory should be moved to /usr. What would be the benefit to duplicate files like vmlinuz-version, xen.gz or grub2/* out of /usr back to /boot?
For the kernel there is no duplication if /boot is on the same volume. Those grub files on the other hand already are copies today.
Those who currently must use a dedicated /boot, because they have to use an incapable bootloader, could adjust their fstab and mount the thing on /usr/boot instead, and everything will likely continue to work for them. Such setups can not benefit from the single atomic snapshot anyway.
I believe we cannot avoid improving the tooling to manage the boot files better. The tool has to be aware of the available snapshots/OS revisions and configure the bootloader, generate the initrd, copy/link the kernel etc accordingly. Having rpm drop the kernel unconditionally into /boot and then some %post script that generates the initrd and updates grub has been fragile always. "incapable" bootloader might be considered a feature rather than a bug btw :-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg)