|
From: | Maxim Cournoyer |
Subject: | [bug#37305] [PATCH v3] Allow booting from a Btrfs subvolume |
Date: | Sun, 17 May 2020 12:13:34 -0400 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hi Pierre! Pierre Neidhardt <address@hidden> writes: > I'll try to test this patch, possibly today. > > Is the patch from the 18th of March the right one? > The patch says it has 5 components but the last patch is > > [PATCH 4/5] bootloader: grub: Allow booting from a Btrfs subvolume. > > Is the fifth patch missing? As I send my patches as attachments rather than with git send-email, I simply forgot to update the subject line counter. There are four patches in total, although the hack in 0001 was controversial so is included as a curiosity only. I've rebased the 4 patches on current master, and fixed some conflict that arose in the initrd code.
0001-gnu-tests-Reduce-the-time-required-to-run-the-system.patch
Description: Text Data
0002-linux-boot-Refactor-boot-system.patch
Description: Text Data
0003-file-systems-Add-helpers-for-parsing-the-options-str.patch
Description: Text Data
0004-bootloader-grub-Allow-booting-from-a-Btrfs-subvolume.patch
Description: Text Data
I'll test those rebased patches as well. The automated system tests no longer pass -- although it might not be specific to this change (I'll try running the "installed-os" test to see if all the install tests are broken or just this new "btrfs-root-on-subvolume-os" one.). In case you are not familiar with system tests, a single system test can be run with: make check-system TESTS="btrfs-root-on-subvolume-os" The install tests are defined under (gnu tests install) and are *very* expensive to run (mostly in time, but they require some disk space as well). Hence the hack in 0001, but I'm not sure if it brings as much benefits as when I made it (given Ludovic keeps improving the way Guix gets built :-)). A fresh benchmark could be interesting if you have lots of time on your hands. Thank you for looking at this! Maxim
[Prev in Thread] | Current Thread | [Next in Thread] |