https://bugzilla.novell.com/show_bug.cgi?id=224476
User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=224476#c26
Josef Reidinger jreidinger@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |mrmazda@ij.net
--- Comment #26 from Josef Reidinger jreidinger@novell.com 2008-09-26 02:22:14 MDT --- (In reply to comment #25 from Felix Miata)
Other distros don't depend on /etc/grub.conf, so average users don't know when they "check booting settings" that it exists and should look at or change it. mkinitrd and/or YaST if they insist to use this file should either perform a sanity check on it before using it, (comment 0) or issue a warning so the user can discover this file exists and may need modification.
I don't know what you mean by "propose new in yast bootloader". All I did was rpm -ivh a kernel. That followed a typical upgrade that followed an (atypical) partition move accompanied by manually and successfully reconfiguring the standard boot config files fstab and menu.lst.
Would it be so hard to add a sanity check of grub.conf before using it?
Yes, it is quite problem, because during kernel upgrade you don't touch it (don't change it). Perl-Bootloader only use it as grub --batch < /etc/grub.conf. But you are right, that it need to be documented. Where you expect this documentation?