[opensuse-packaging] Running mkinitrd in %unpost and %post
Hello list-mates, Currently, if you uninstall bootsplash from your system, you'd see the boosplash image when you boot up/shutdown your computer. Is it a good idea to run mkinitrd in %postun so that you get no bootsplash image after uninstalling it? I think it makes sense. %postun %{insserv_cleanup} /sbin/mkinitrd_setup +if test -s /etc/sysconfig/bootloader ; then +/sbin/mkinitrd +fi Furthermore, some people have reported that they get no bootsplash after a KDE install from the 11.4 Net ISO. Besides this, I have added support for more resolutions. So, I was also thinking about running mkinitrd in % post to make sure they get a bootsplash image %post %{fillup_only -ns bootsplash branding-openSUSE } perl -pi -e 's/^(THEME=).*/$1"openSUSE"/' /etc/sysconfig/bootsplash +if test -s /etc/sysconfig/bootloader ; then +/sbin/mkinitrd +fi What I don't want is users suffering due to lots of mkinitrds. How probable would having updates/installs that run mknitrd several times be? Greetings, -- Javier Llorente
* Javier Llorente (javier@opensuse.org) [20110315 23:39]:
Currently, if you uninstall bootsplash from your system, you'd see the boosplash image when you boot up/shutdown your computer.
If you boot with the splash=verbose kernel option you won't get to see the splash. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Javier Llorente
-
Philipp Thomas