On 2013-07-19 10:50 (GMT+0200) Stefan Seyfried composed:
Felix Miata, in English, wrote:
On 2013-07-18 12:29 (GMT+0200) Andreas Schwab composed:
I don't understand what you are after. The fact that gfxboot depends on a fixed perl version has not changed in any way.
Something must have changed somehow. I used to be able to keep /boot/message from being rewritten without applying chattr +i to it. In
mv /boot/message /boot/mymessage sed -i 's#/boot/message#/boot/mymessage#' /boot/grub/menu.lst
done. If you have /boot not on the root partition, just edit menu.lst by hand. I'm sure you get the idea.
I had that idea. It's no more than a marginally acceptable workaround. /boot/message is customizable, like such things as /etc/HOSTNAME, /etc/resolv.conf, /etc/samba/smb.conf, /etc/exports & etc. It doesn't live in /usr or /bin or /sbin or /run or /lib. So, user customizations should not be stripped or altered at update times. Incompatible changes need to go in .rpmnew files instead of destroying customizations made via gfxboot --change-config. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org