Bug 86006

Summary: up2date lilo cut map-drive ... to ....
Product: [Retired] Red Hat Linux Reporter: Need Real Name <jf>
Component: up2dateAssignee: Bret McMillan <bretm>
Status: CLOSED WONTFIX QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: gafton, mihai.ibanescu
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-22 15:33:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2003-03-12 06:56:53 UTC
Description of problem:
I've linux on /dev/hda and Windows on /dev/hdb, so in my lilo.conf I've an entry
like this:
other=/dev/hdb1
	label=WinXP
	map-drive=0x81
	to=0x80
	map-drive=0x80
	to=0x81
	table=/dev/hdb
When I up2date the kernel it cut my entry in lilo.conf like this
other=/dev/hdb1
	label=WinXP
	map-drive=0x81
	to=0x80
        table=/dev/hdb

The second map-drive was cut !


Version-Release number of selected component (if applicable):
redhat 7.3
lilo-21.4.4-14
up2date-2.8.39-1.7.3

How reproducible:


Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:

Comment 1 John Thacker 2006-04-22 15:33:04 UTC
In any case, up2date is no longer shipped with Fedora Core; its functionality 
has been replaced by pup, found in the pirut package.  The only fixes 
likely to be made to up2date in RedHat Linux and earlier Fedora Core 
versions are security fixes by Fedora Legacy.  This does not seem to 
be a security bug, so I'm closing it.

If the problem is appropriate to RHEL and occurs to a user there, it 
can be filed as such.

Comment 2 David Lawrence 2006-04-24 19:19:48 UTC
Adding to blocker bug 185483 and also adding IBM confidential group.

Comment 3 David Lawrence 2006-04-24 19:37:45 UTC
Oops. I am sorry for these changes. I searched on the wrong bug list and
mistakenly made these changes. Removing from blocker bug 185483 and also
removing IBM confidential group.