Mailinglist Archive: yast-devel (42 mails)

< Previous Next >
Re: [yast-devel] broken GUI installer
On 2014-05-01 03:59 (GMT-0400) Andrey Borzenkov composed:

รท Wed, 30 Apr 2014 06:53:24 -0400 Felix Miata composed:

Also, I'm particularly unhappy that 13 month old
https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented,

grub2 defaults to os-prober disabled with exact the same result as
requested - only entries for current OS are present in menu.

I wouldn't know what Grub2 under openSUSE does. As long as any installer offers an option to install Grub Legacy, that's what I choose. When given only the choices no bootloader at all or Grub2, I choose no bootloader at all. I'm sure I'm not the only one who prefers the simplicity of the vastly lighter weight Grub that never complains about reliability when it can't commandeer the boot track, and never declares on boot that the perfectly valid vga= cmdline option for gfxchips lacking KMS support is deprecated.

As such times as I want to know about Grub2, I boot *buntu (which is almost the only use I ever have for *buntu, or any Debian for that matter). So, I am familiar enough with Grub2 to know I don't want it replacing Grub Legacy on any system that doesn't require something that Grub Legacy cannot provide.

While most users apparently think that YaST is the most important openSUSE standout against competitors, I find openSUSE's Grub Legacy Gfxboot menu another feature without comparison, and a sleeping dog that for most users does not need to be awakened.

which wouldn't even be needed if there was a checkbox to say new bootloader is
or is not to
be the master bootloader (aka stanzas for any but new OS desired or necessary).

This could relatively easy be implemented by allowing no "status
location" in bootloader dialog. This would avoid physically installing
bootloader while still generating all needed files. Actually, I believe
at least for grub2 this may work already - pbl just loops over locations
and installs on each one; if no location is selected, it should do
nothing. I'm just not sure whether YaST/glue libraries support it.

Something seems lost in translation. I don't want to have to choose between installation of either no bootloader at all, or installation of a bootloader that wants to be master of all systems installed. I want Grub Legacy on the / partition, and would much prefer for it to get there the same way it has ever since before openSUSE 10.0 was released, via YaST, and with the added simplicity of only the two stanzas that unconditionally make sense for a new installation. I'm certainly capable of managing my own systems' bootloaders without help of scripts or YaST, but to assist over the phone, via email or in web forums I much prefer coaching people through the overall simpler choice that is the senior Grub that only requires two short and simple shell commands to set up, and without even having to mount the target for them to work.
--
"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: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation
References