Re: new packaging of the kernel/mkinitcpio/kmod

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



> ----------------------------------------
> From: Eli Schwartz via arch-general <arch-general@xxxxxxxxxxxxx>
> Sent: Fri Nov 01 23:06:03 CET 2019
> To: <arch-general@xxxxxxxxxxxxx>
> Cc: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
> Subject: Re:  new packaging of the kernel/mkinitcpio/kmod
> 
> 
> Dracut does not work out of the box (we currently patch it to not use a
> nonexistent tool, and the same patch is now in upstream master but with
> no release in sight), and has issues like the tests failing on
> non-Redhat systems.
> 
> Our dracut packager tried to get in touch with the dracut developer,
> after a lack of success for quite some time it seems that the individual
> in question was on... parental leave, IIRC? I'm not sure what the
> current status is.
> 

In such cases using tip of git branch would help.

> So the jury is still out on whether dracut or mkinitcpio is more work. ;)
> 

Making dracut work initially may need some work but after that it will just work.
There is also 3rd-party initramfs modules developer perspective where coding
something once which then will work on all distros (as dracut is supported in
fedora/rhel, ubuntu/debian, suse, etc.) makes life easier than having to support
each distro separately. Fragmentation is big issue as always.

Yours sincerely

G. K.



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux