diff options
author | WorMzy Tykashi <wormzy.tykashi@gmail.com> | 2014-03-03 02:17:29 +0100 |
---|---|---|
committer | Dave Reisner <dreisner@archlinux.org> | 2014-03-05 03:30:11 +0100 |
commit | bbda33a25dc5f0da89f92fb30aaa40d88b7f06ac (patch) | |
tree | 560e9242c5ce3756cd9e77f80646794731748c82 /systemd | |
parent | 869c314159497c74aa6cf477862629b05a9fd2b0 (diff) | |
download | mkinitcpio-bbda33a25dc5f0da89f92fb30aaa40d88b7f06ac.tar.gz mkinitcpio-bbda33a25dc5f0da89f92fb30aaa40d88b7f06ac.tar.xz |
add btrfs module quirk for linux 3.14
This patch adds in some extra hackery to make sure that users with btrfs
root filesystems don't end up with unusable initrds due to the following
change made upstream [1]. TL;DR: The btrfs module has dropped it's
libcrc32c dependency, so mkinitcpio no longer pulls in the crc32c module
necessary for the btrfs module to be inserted. The crc32c module was
only pulled in previously due to mkinitcpio hackery [2], so extra
hackery now seems like the logical path.
This problem can be experienced by using linux-mainline on an Arch
machine with a btrfs root filesystem. Besides from this extra hackery,
an alternative workaround would be for users in this situation to add
crc32c to their MODULES aray in their mkintcpio.conf. Of course, this
needs to be done ahead of the linux-3.14 upgrade for them to avoid the
problem (assuming none of their other modules depend on libcrc32c).
[1] http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg30912.html
[2] https://projects.archlinux.org/mkinitcpio.git/tree/functions?id=v16#n398
Diffstat (limited to 'systemd')
0 files changed, 0 insertions, 0 deletions