summaryrefslogtreecommitdiffstats
path: root/tools/drakx-in-chroot
diff options
context:
space:
mode:
authorColin Guthrie <colin@mageia.org>2012-09-01 15:47:19 +0000
committerColin Guthrie <colin@mageia.org>2012-09-01 15:47:19 +0000
commit84779a4ad529caf0afa666a2a05978d72316340a (patch)
treebb8af71fa5adeed85c4f38a3fed0d770e6cfc35b /tools/drakx-in-chroot
parentb19cfe25e416028f891b28b692817d529a1cc016 (diff)
downloaddrakx-84779a4ad529caf0afa666a2a05978d72316340a.tar
drakx-84779a4ad529caf0afa666a2a05978d72316340a.tar.gz
drakx-84779a4ad529caf0afa666a2a05978d72316340a.tar.bz2
drakx-84779a4ad529caf0afa666a2a05978d72316340a.tar.xz
drakx-84779a4ad529caf0afa666a2a05978d72316340a.zip
(update_splash) Only expand initrd symlinks for kernels with vga=nnn arguments
When working out which initrds to regenerate, it is likely that the same initrd symlink is used by multiple bootloader entries (i.e. typically the initrd.img symlinked initrd is used by both the current and the failsafe entry). If the earlier entry does have vga= but the latter entry does not, then the latter entry will end up being the value used when checking the vga= argument when deciding if the initrd needs to be regenerated. Thus we only expand the symlink if the vga= value is set which means that any initrd that needs to be regenerated definitely will be regenerated. This will hopefully solve the problem seen on mga2 when and updated theme package had to be pushed but the initrds didn't seem to be updated.
Diffstat (limited to 'tools/drakx-in-chroot')
0 files changed, 0 insertions, 0 deletions