![](https://seccdn.libravatar.org/avatar/482b6c0369f4709de8faa6843cd6b347.jpg?s=120&d=mm&r=g)
On Tuesday 18 March 2014 11.46:00 Jeff Mahoney wrote:
On 3/18/14, 5:49 AM, Andreas Schwab wrote:
Cristian Rodríguez <crrodriguez@opensuse.org> writes:
Yes, you can do that.. however...AFAIK it will require a change in zypp to be effective, since last time I checked, packages were installed one by one and not in a one-shot RPM transaction.
libzypp in Factory now collects all %posttrans scriptlets into /var/adm/update-scripts and executes them at the end.
\o/
Yes, please. There are so many packages other than just the kernel that cause a mkinitrd to be invoked. I would be very happy for that to happen just once.
and having a flag in mkinitrd to use pigz if installed would also be a big win. gzip -d initrd-3.13.6-1.g4727218-desktop -c > /tmp/initrd-test time pigz -9 -k initrd-test real 0m10.356s user 1m17.555s sys 0m0.183s time gzip -9 -k initrd-test real 1m15.489s user 1m15.370s sys 0m0.077s ll initrd* -rw-r--r-- 1 root root 101707264 Mar 19 17:50 initrd-test -rw-r--r-- 1 root root 35365962 Mar 19 17:50 initrd-test.gz -rw-r--r-- 1 root root 35351822 Mar 19 17:50 initrd-test.pigz 1 minutes 05 * by the number of kernel/initrd present on the computer.
Question, though: What happens if the kernel package is updated and the transaction is interrupted? Is the old kernel package still around? Would we end up with an unbootable system?
We have multi-kernel yes by default, the worst case being still an interrupt during the mkinitrd touching the previously installed and working initrd ... But this is not new as single point of failure. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot