Mailinglist Archive: opensuse (878 mails)

< Previous Next >
Re: [opensuse] editing boot menu (was: Improved perform...)
On 2013-09-20 23:09 (GMT+1000) Basil Chupin composed:

James Knott wrote:

BTW, I can easily tell what the change was in the grub menu, as on new
installation, or kernel update, the menu lists the kernel version
number. I always edit that down to just "Desktop" and "Failsafe" and
get rid of the version number etc.

Why do you wanna do that for? :-) Does the Does the version number
give you nightmares or sumthin'? :-)

It reminds me of Windows, where app installation habitually appends a version number to an application title, not a whole lot unlike underscore-littered libs like libpython2_7-1_0 or libgimp-2_0-0 or backends like gstreamer-0_10. Current/latest kernel's version number doesn't need to be in the default or latest failsafe stanzas. It's obfuscatory noise.

I never touch anything in there 'cause messing around with anything
grub/bootloader is just asking for trouble :-) .

No trouble here except for yast2-bootloader habitually disobeys my configuration specifications in /etc/sysconfig/bootloader.

"If it ain't broke don't fix it", as the Actress said to the Bishop.

"Ain't broke" is your assumption. Here, the only time running yast2-bootloader doesn't disfigure my menu.lst is when it follows uninstalling a kernel. On my systems the correct place for the digit to override the default target belongs as the last cmdline option, but yast2-bootloader always puts it elsewhere. Thus after every kernel installation I need to clean up after yast2-bootloader by manually editing menu.lst.

c.f.
https://bugzilla.novell.com/show_bug.cgi?id=643984
https://features.opensuse.org/310673
--
"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+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups