https://bugzilla.suse.com/show_bug.cgi?id=1190567 https://bugzilla.suse.com/show_bug.cgi?id=1190567#c7 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Marcus Schaefer <ms@suse.com> --- We fixed the integration tests that tested boot on an extra partition by code that resolves the symlink back to be no link anymore. This fixes our tests. What stays imho is some smell for everybody that wants to build an image were /boot and /usr is not the same storage. That opened a can of worms and some extra code in the kernel post scripts.

The OS moves to /usr and /usr only. Those symlinks are only created for >compatibility until the tooling around bootloaders is adopted.

That's fine by me. So /boot will go away from Linux ? That's the driver right ? In this case I'm still confused were the value is in such a change, or in other words what is wrong with /boot and why did it harm users to have data in /boot such that it has to move to /usr I'm asking this to have a good answer to all the people which will come across the appliance building way. Thanks -- You are receiving this mail because: You are the assignee for the bug.