Mailinglist Archive: opensuse-bugs (13042 mails)

< Previous Next >
[Bug 465148] New: Update still destroys custom menu.lst
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 10 Jan 2009 18:07:30 -0700 (MST)
  • Message-id: <bug-465148-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=465148


Summary: Update still destroys custom menu.lst
Classification: openSUSE
Product: openSUSE 11.1
Version: RC 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Update Problems
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: andi-nbz@xxxxxxxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
Found By: ---


User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10
(like Gecko) SUSE
Build Identifier:


Another update, another destroyed menu.lst. I keep
complaining about this for at least three releases,
but it seems to get constantly worse.

The new problem is that 11.1 now adds empty
initrd lines to entries which don't have an initrd,
but that obviously makes grub stop then. So
if there's no initrd line before don't add a new
one.

The other issue is that it still keeps rewriting
root=/dev/sdXX entries to the long form
even when the entry has no initrd. But since
the long form is only parsed by the initrd
this __ALWAYS__ leads to a non booting entry.
So if there's no initrd line don't rewrite
the root= entry.

The third is that it always reorders entries
and puts my custom entries on the end. That
breaks the testing scripts which use a number
for "grubonce". So don't reorder the entries
when writing it out.

And before you ask: yes kernel hackers run
kernels without initrd. And they get frustrated
when each update doesn't boot because of that.

Thanks.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >