Skip to content
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

Rerun writeBootLoader on Live BTRFS installs #617

Closed
wants to merge 1 commit into from

Conversation

bcl
Copy link
Contributor

@bcl bcl commented May 5, 2016

In order to support installation of live media without an initramfs (to
save space) this reruns writeBootLoader for all live BTRFS
installations. This will also fix the missing initrd line when
/boot is on BTRFS (see rhbz#1200539).

Without this the initial grub2-mkconfig without an initramfs doesn't
build the kernel cmdline correctly. On live installations the initramfs
is always rebuilt, but that happens after the initial call to
writeBootLoader.

In order to support installation of live media without an initramfs (to
save space) this reruns writeBootLoader for all live BTRFS
installations. This will also fix the missing initrd line when
/boot is on BTRFS (see rhbz#1200539).

Without this the initial grub2-mkconfig without an initramfs doesn't
build the kernel cmdline correctly. On live installations the initramfs
is always rebuilt, but that happens after the initial call to
writeBootLoader.
# This works around 2 problems, /boot on BTRFS and BTRFS installations where the initrd is
# recreated after the first writeBootLoader call. This reruns it after the new initrd has
# been created, fixing the kernel root and subvol args and adding the missing initrd entry.
boot_on_btrfs = isinstance(storage.mountpoints.get("/"), BTRFSDevice)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if / is not a BTRFSDevice, but /boot is? (if we support something like that)

@bcl
Copy link
Contributor Author

bcl commented May 7, 2016

What if / is not a BTRFSDevice, but /boot is? (if we support something like that)
Add a line note

I don't think that's possible, or likely. I'm also pretty sure we're currently not supporting /boot on btrfs because of the previous issues.

@vpodzime
Copy link
Contributor

vpodzime commented May 9, 2016

I don't think that's possible, or likely. I'm also pretty sure we're currently not supporting /boot on btrfs because of the previous issues.

Works for me.

@vpodzime vpodzime added the ACK label May 9, 2016
@bcl bcl added master Please, use the `f39` label instead. f24-branch labels May 10, 2016
@bcl bcl removed the f24-branch label Jun 14, 2016
@bcl
Copy link
Contributor Author

bcl commented Jun 14, 2016

Pushed to master only.

@bcl bcl closed this Jun 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master Please, use the `f39` label instead.
2 participants