https://bugzilla.novell.com/show_bug.cgi?id=395085
User aosthof@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395085#c15
Alexander Osthof changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|aosthof@novell.com |juhliarik@novell.com
Status|ASSIGNED |NEW
--- Comment #15 from Alexander Osthof 2008-06-03 10:10:39 MDT ---
Alright, I've spent quite some hours in debugging this problem, but the deeper
I dug the more I thought this is no perl-Bootloader problem. So here are the
scenarios I've tried:
- Installed openSUSE 11.0 RC1 on a primary partition besides an already
existent openSUSE 10.3 on an extended partition
--> no configfile section for openSUSE 10.3 on other partition created
- Installed openSUSE 11.0 RC1 including a new perl-Bootloader package on
a primary partition besides an already existent openSUSE 10.3 on an
extended partition
--> no configfile section for openSUSE 10.3 on other partition created
- Installed openSUSE 10.3 GM on a primary partition besides an already
existent openSUSE 10.3 on a extended partition
--> configfile section for openSUSE 10.3 on other partition gets created
- Installed openSUSE 11.0 RC1 on a primary partition using 10.3's
perl-Bootloader package besides an already existent openSUSE 10.3 on an
extended partition
--> no configfile section for openSUSE 10.3 on other partition created
So to say, the perl-Bootloader package couldn't be the problem, as it works
with openSUSE 10.3.
Moreover, I've took a look on the bootloader menu.lst proposal during the
installation. The proposal there looks bad already, the (wannabe) configfile
section only consists of a label and a (e.g.) "root (hd1,4)" line.
I'll attach the y2log file which logged the workflow until the boot proposal.
--
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.