On 2017-05-15 02:01, Felix Miata wrote:
Carlos E. R. composed on 2017-05-15 01:41 (UTC+0200):
Felix Miata wrote:
Even not accepting btrfs in the first place is easier said than done: # zypper -v in dracut ... Selecting 'dracut-044-25.1.x86_64' from repository 'OSS' for installation. ... Problem: dracut-044-25.1.x86_64 requires btrfsprogs >= 3.18, but this requirement cannot be provided uninstallable providers: btrfsprogs-4.10.2-1.1.i586[OSS] btrfsprogs-4.10.2-1.1.x86_64[OSS] Solution 1: Following actions will be done: remove lock to allow installation of btrfsprogs-4.10.2-1.1.i586[OSS] install btrfsprogs-4.10.2-1.1.i586 despite the inferior architecture Solution 2: remove lock to allow installation of btrfsprogs-4.10.2-1.1.x86_64[OSS] Solution 3: do not install dracut-044-25.1.x86_64 Solution 4: break dracut-044-25.1.x86_64 by ignoring some of its dependencies
:-(
You can have btrfsprogs installed, yet not a single btrfs partition installed.
Anything not strictly required, that could be recommended or suggested but is packaged as required, constitutes bloat:
wastes initrd build time wastes initrd storage space wastes initrd load time wastes storage space wastes updates bandwidth
A little bloat here, a little bloat there, adds up to more than a little.
Fighting those wastes more time than it is worth. Anyway, if there is no btrfs partition I do not see a reason for dracut to include modules to mount or repair them, in the dracut image. Yet the package can require them as an install requirement, different from a runtime requirement. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))