-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move OEM mount point out of /usr #766
Labels
Comments
pothos
moved this to Upcoming / Backlog
in Flatcar tactical, release planning, and roadmap
Jun 8, 2022
pothos
moved this from Upcoming / Backlog
to Planned / ToDo
in Flatcar tactical, release planning, and roadmap
Jun 8, 2022
pothos
changed the title
[RFE] Move OEM mount point out of /usr
Move OEM mount point out of /usr
Jun 8, 2022
pothos
moved this to Upcoming / Backlog
in Flatcar tactical, release planning, and roadmap
Jan 4, 2023
9 tasks
Since we also mount the OEM partition from the initrd under |
krnowak
moved this from Upcoming / Backlog
to In Progress
in Flatcar tactical, release planning, and roadmap
Apr 4, 2023
Yeah, that's what I'm using. |
4 tasks
pothos
moved this from ⚒️ In Progress
to Implemented
in Flatcar tactical, release planning, and roadmap
May 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current situation
The OEM partition is mounted under
/usr/share/oem/
which requires a workaround for systemd-sysext because the management of the overlay mounts on/usr
results in the OEM mount point to be lost without the workaround.Impact
We had to add a special handling for the OEM mount point in the systemd-sysext service. Users manually invoking
systemd-sysext
will lose the partition mount - while we don't support manual usage of the CLI command for the reason that it doesn't reload and start new services, this is a lesser evil than a broken system because of the OEM partition being inaccessible.Ideal future situation
We can drop the special handling because the OEM partition is mounted elsewhere, e.g., under
/oem/
and a symlink from/usr/share/oem/
exists for backwards compatibility.Implementation options
Additional information
/usr/lib/systemd/system/systemd-sysext.service.d/10-mount-oem-partition.conf
is the workaroundThe text was updated successfully, but these errors were encountered: