Mailinglist Archive: opensuse-packaging (216 mails)
| < Previous | Next > |
[opensuse-packaging] Running mkinitrd in %unpost and %post
- From: Javier Llorente <javier@xxxxxxxxxxxx>
- Date: Tue, 15 Mar 2011 23:40:50 +0100
- Message-id: <201103152340.52604.javier@opensuse.org>
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
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
| < Previous | Next > |