-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add GRUB static config migration as sub command #789
Comments
travier
added a commit
to travier/bootupd
that referenced
this issue
Dec 12, 2024
travier
added a commit
to travier/bootupd
that referenced
this issue
Dec 12, 2024
travier
added a commit
to travier/bootupd
that referenced
this issue
Dec 18, 2024
travier
added a commit
to travier/bootupd
that referenced
this issue
Dec 18, 2024
Note that the service is intentionally not enabled by default as it should be up to the distribution to add a systemd preset if the migration to a static GRUB config is needed. This will be used on Atomic Desktops & IoT systems to migrate systems to a static GRUB config before enabling composefs as GRUB curently does not interact well with it: https://bugzilla.redhat.com/show_bug.cgi?id=2308594 See: coreos#789 See: https://fedoraproject.org/wiki/Changes/ComposefsAtomicDesktops
travier
added a commit
to travier/bootupd
that referenced
this issue
Dec 18, 2024
travier
added a commit
to travier/bootupd
that referenced
this issue
Dec 18, 2024
Note that the service is intentionally not enabled by default as it should be up to the distribution to add a systemd preset if the migration to a static GRUB config is needed. This will be used on Atomic Desktops & IoT systems to migrate systems to a static GRUB config before enabling composefs as GRUB curently does not interact well with it: https://bugzilla.redhat.com/show_bug.cgi?id=2308594 See: coreos#789 See: https://fedoraproject.org/wiki/Changes/ComposefsAtomicDesktops
curious, what / where is the original script ? |
I initial worked on it in https://hackmd.io/B8lMCzLFQjGgr5jhl_Iw-w and posted it to https://gitlab.com/fedora/ostree/sig/-/issues/35. |
travier
added a commit
to travier/bootupd
that referenced
this issue
Jan 23, 2025
travier
added a commit
to travier/bootupd
that referenced
this issue
Jan 23, 2025
Note that the service is intentionally not enabled by default as it should be up to the distribution to add a systemd preset if the migration to a static GRUB config is needed. This will be used on Atomic Desktops & IoT systems to migrate systems to a static GRUB config before enabling composefs as GRUB curently does not interact well with it: https://bugzilla.redhat.com/show_bug.cgi?id=2308594 See: coreos#789 See: https://fedoraproject.org/wiki/Changes/ComposefsAtomicDesktops
travier
added a commit
to travier/bootupd
that referenced
this issue
Jan 27, 2025
Add a hidden subcommand that migrates existing systems using a dynamic GRUB config to a static one. This command is expected to be run after a successful bootloader update. One way to do that is to add it as a droppin unit config for the `bootloader-update.service` unit included in this repo: ``` $ cat /usr/lib/systremd/system/bootloader-update.service.d/migrate-static-grub-config.conf [Service] ExecStart=/usr/bin/bootupctl migrate-static-grub-config ``` This will be used on Atomic Desktops & IoT systems to migrate systems to a static GRUB config before enabling composefs as GRUB curently does not interact well with it [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2308594 See: https://gitlab.com/fedora/ostree/sig/-/issues/35 See: https://pagure.io/workstation-ostree-config/pull-request/591 See: https://fedoraproject.org/wiki/Changes/ComposefsAtomicDesktops Fixes: coreos#789
travier
added a commit
to travier/fedora-atomic-desktops-devel
that referenced
this issue
Feb 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should convert the script to Rust and include it in bootupd so that it can be used by both IoT & Atomic Desktops directly.
See: https://pagure.io/workstation-ostree-config/pull-request/591
See: https://gitlab.com/fedora/ostree/sig/-/issues/35
The text was updated successfully, but these errors were encountered: