Bug 1218817 - u-boot: move to /usr
Summary: u-boot: move to /usr
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Guillaume GARDET
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1029961
  Show dependency tree / graph
 
Reported: 2024-01-15 14:19 UTC by Ludwig Nussel
Modified: 2024-01-15 14:19 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ludwig Nussel 2024-01-15 14:19:42 UTC 
One of the motivations for UsrMerge is to have all read-only parts of
the operating system in /usr. The u-boot packages install files in /boot/vc
though which isn't in line with that idea. Having u-boot installed via rpm in /boot may also cause inconsistencies with snapshots as /boot is a separate partition.

So it makes sense to store the rpm provided parts of the u-boot packages where the rest of the OS is and manage /boot separately.

Now the question is how and where. So far update-bootloader is in charge of updating e.g. grub. Update-bootloader is unaware that we are actually using u-boot+grub2 as bootloader though. On rpi it's even rpi-firmware+u-boot+grub2.

Maybe u-boot could install itself into a hierarchy in e.g /usr/lib/boot, resembling the actual layout that should be in /boot. The efi parts could go to /usr/lib/efi. Update-bootloader would then just sync the content of those directories to the boot resp efi partitions. That way update-bootloader doesn't actually need to know about those extra layers.

Thoughts?