On Thu, Jun 8, 2017 at 4:25 PM, Christian Ehrhardt < christian.ehrha...@canonical.com> wrote:
> > On Thu, Jun 8, 2017 at 1:01 AM, Ritesh Raj Sarraf <r...@debian.org> wrote: > >> >> Are multipath's hooks compatible with Dracut ? Have you tested the >> combination >> of multipath and Dracut ? > > > I haven't since as outlined above the idea of this change was more about > dependency management than a replacement (which is why it is an or), but it > is actually a good idea to try. I keep the task to do so with me and will > ping you once I got to it. > I tested a bit. First of all the hooks depend on /usr/share/initramfs-tools/hook-functions, but that is kind of ok as initramfs-tools-core stays installed when switching to dracut. But Dracut does not consider the initramfs-tools. Instead it has a system called "modules" which still are scripts. Dracut delivers some multipath functions for that in package "dracut-core" and places it in /usr/lib/dracut/modules.d/90multipath It does similar things, installing services and rules - but in a totally different way. So TL;DR no, dracut is not fully compatible. I know the suggested change was about making the other package installable and not to work perfectly. But I think multipath-tools is fine atm. Because: 1. only multipath-tools-boot depends on initramfs-tools 2. as we just found it really "depends" and dracut is no alternative People can ignore-deps if they want to force it half working 3. the -boot package is AFAIK clearly not default installed, even if you install multipath-tools it is only suggested. => That said dracut is installable as it should be unless one explicitly fetched multiapth-tools-boot and then it is correct to conflict. Thanks for making me check that in Detail Ritesh. Closing the bug now.