Michal Suchánek wrote:
On Mon, Apr 19, 2021 at 06:58:25PM +0200, Ludwig Nussel wrote:
Michal Suchánek wrote:
On Mon, Apr 19, 2021 at 06:06:47PM +0200, Ludwig Nussel wrote:
Olaf Hering wrote:
Am Mon, 12 Apr 2021 10:46:48 +0200 schrieb Ludwig Nussel
: Does anyone have a better idea or can we just follow Fedora's approach here?
Since the reasons for "/boot" are obsolete since more than a decade, just go ahead.
Just make sure to provide the equivalent of "/boot/vmlinuz" and "/boot/initrd", a pointer to the last installed kernel. This can very well be stored somewhere in "/usr".
Here's my suggestion to move the kernel related read-only files from /boot to /lib/modules/%kernelrelease-%build_flavor
What do we get exactly by moving from /boot to /lib?
Isn't /lib as much obsolete as /boot?
Yes and no. In the usrmerge case /lib is a symlink to /usr/lib. RPM happily follows that. So there is no urgent need for packages to actually install to /usr. That's why I so far did not touch any packages that do not produce a usrmerge conflict. Longer term I suppose we do want to adjust all packages to install into /usr for consistency.
So we do not need to serialize the efforts and wait for usrmerge to actually happen.
On the other hand, if we expect that the kernel needs to be adjusted again to install into usr maybe it makes sense to do in one go rather than having 3 different variants of where kernel installs.
Sure, fair point. If timing is the only concern I'd count that as +1 on the general approach at least :-) Btw talking about different variants where the kernel installs... Would it make sense to have a consistent kernel file name across architectures? Right now it might be vmlinuz, vmlinux, Image, image or zImage¹. cu Ludwig [1] https://github.com/openSUSE/installation-images/blob/master/etc/config#L16 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg)