03.04.2012 16:41, Colin Guthrie kirjoitti: > Hi, > > With a memory of the infamous "initrd killer" problem that is still > lurking in the background somewhere, something related to theme updates > is messing things up: > > e.g. see the before and after listings for my /boot > > > [colin@jimmy code (master)]$ ll /boot > total 39784 [...] > lrwxrwxrwx 1 root root 31 Apr 3 09:22 initrd.img -> > initrd-3.3.1-desktop-1.mga2.img [...]
> > After: > > [colin@jimmy code (master)]$ ll /boot [...] > -rw-r--r-- 1 root root 7556648 Apr 3 14:33 initrd.img [...] Reproduced: root 9723 0.0 0.0 25760 1372 pts/11 S+ 03:02 0:00 | \_ /bin/sh /usr/share/bootsplash/scripts/switch-themes Mageia-Default root 9745 0.2 0.2 93496 20724 pts/11 S+ 03:02 0:00 | \_ /usr/bin/perl /usr/sbin/bootloader-config --action update-splash root 30133 0.0 0.0 25760 1312 pts/11 S+ 03:06 0:00 | \_ /bin/sh /usr/share/bootsplash/scripts/make-boot-splash /boot/initrd.img 800 root 30143 0.0 0.0 25760 1340 pts/11 S+ 03:06 0:00 | \_ /bin/sh /usr/share/bootsplash/scripts/make-boot-splash-raw /boot/initrd.img Mageia-Default => bork So it seems like some recent change in DrakX which causes it to call make-boot-splash even for /boot/initrd.img... -- Anssi Hannula