Bug 119807 - LILO makes wrong configuration
Summary: LILO makes wrong configuration
Status: RESOLVED DUPLICATE of bug 119174
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: PC All
: P5 - None : Critical
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-01 15:12 UTC by Hernan Diego
Modified: 2005-10-04 10:54 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hernan Diego 2005-10-01 15:12:08 UTC 
I have two hard disk. Windows in hda, OpenSuse in hdb. Bootloader of Windows on
hda, installing lilo on MBR of hdb
My BIOS is set to boot from second hard disk first.
I wish to configure lilo on MBR in hdb (my firs boot device).
To boot windows, lilo.conf must have the following entries in Windwos section:

other = /dev/hda1
label = Windows
table = /dev/hda
map-drive = 0x80
 to = 0x81
map-drive = 0x81
 to = 0x80

When Yast configures lilo, it doesn't configure Windows (and I think Yast must
do), but if I modify by hand lilo.conf, when a new kernel is installed, Yast
overwrite my entries in lilo.conf, deleting "table = ..." and "map-drive = ...",
resulting I can't boot to windows, I need to modify again my lilo.conf etc..

Mandrake/Mandriva handles this special case well, detects windows on hda, linux
on hdb and remaps the drives.
Comment 1 Jiri Srain 2005-10-04 10:54:31 UTC 
Making duplicate of same issue with GRUB. 

*** This bug has been marked as a duplicate of 119174 ***