[Mageia-dev] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

Sun Mar 25 21:56:59 CEST 2012

'Twas brillig, and Luc Menut at 25/03/12 20:55 did gyre and gimble:
+> Le 25/03/2012 19:08, Colin Guthrie a écrit :
+>> 'Twas brillig, and Luc Menut at 25/03/12 17:35 did gyre and gimble:
+>>> Le 25/03/2012 17:45, root at mageia.org a écrit :
+>>>> Revision
+>>>>      226393
+>>>> Author
+>>>>      colin
+>>>
+>>> [...]
+>>>
+>>>>
+>>>> +%triggerpostun backend -- drakxtools-backend<   14.1-2
+>>>> +if [ -w /boot/grub/menu.lst ]; then
+>>>> +  if grep -q splash= /boot/grub/menu.lst; then
+>>>> +    echo"Migrating kernel commandline bootsplash arguments in grub"
+>>>> +    sed -i 's/ splash=silent / splash quiet /;s/ splash=silent$/
+>>>> splash quiet/;s/ splash=verbose / /;s/ splash=verbose$//;'
+>>>> /boot/grub/menu.lst
+>>>> +  fi
+>>>> +fi
+>>>> +
+>>>
+>>> IIUC this script, you update splash=silent&  splash=verbose in
+>>> /boot/grub/menu.lst for all the lines.
+>>> What happens if we have entries for mga1 or other distros in the same
+>>> grub menu.lst ?
+>>> Aren't you going to break all these entries with such update?
+>>>
+>>> Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.
+>>
+>> Yeah, good point.
+>>
+>> Any suggestions on how to do this more gracefully?
+> 
+> Nope.
+> 
+> Is this trigger needed for an upgrade mga1->mga2? or is it only for
+> cauldron update?
+> If it's only for cauldron, I think that it would be safer to drop the
+> trigger.
+
+Yeah, it's needed for mga1 -> mga2 upgrade.
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+