Revision as of 17:53, 6 August 2022

Description

This test case creates a dual boot system with two Fedoras of different release versions, using btrfs snapshots, works as expected

create a snapshot
edit the dnfconf,
dup the most recent bls snippet, modify its rootflags entry to match the snapshot name

GRUB menu shows boot options: variant+version+kernelversion for switching between the two.
Can also use grubby --set-default=/boot/vmlinuz-5.18.15-200.fc36.x86_64

@@ Line 6: / Line 6: @@
 # Backup `/boot/efi`, just in case
 |actions=
-#
+# create a snapshot
-#
+# edit the dnfconf,
-#
+# dup the most recent bls snippet, modify its `rootflags` entry to match the snapshot name
+#
+|results=
+# GRUB menu shows boot options: variant+version+kernelversion for switching between the two.
+# Can also use `grubby --set-default=/boot/vmlinuz-5.18.15-200.fc36.x86_64`
+#
+|limitations=
+# /boot is only 1GiB by default, so this is the limiting factor right now, how many Fedoras you can have installed at one time. Two is safe. Three is iffy unless (a) configure the test Fedora instances' dnf.conf such that the kernel is excluded from updates; (b) consider deleting the "rescue" initramfs and kernel for the test instances, also removing `dracut-config-rescue-056-1.fc36.x86_64` from them so these files aren't recreated; or (c) put /boot on a Btrfs subvolume.
 }}