Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 64342

Summary:	does not capture --location=partition
Product:	[Retired] Red Hat Linux	Reporter:	Gene Czarcinski <gczarcinski>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.3
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:	2003-01-30 18:30:52 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:
Bug Depends On:
Bug Blocks:	67218, 79579

Description Gene Czarcinski 2002-05-02 18:16:13 UTC

Description of Problem:
After installing, the anaconda-ks.cfg file does not capture the facte that the
bootloader was installed into the partition rather the MBR.

Version-Release number of selected component (if applicable):


How Reproducible:
everytime

Steps to Reproduce:
1. Install and specify bootload in the partition
2. after reboot, look at anaconda-ks.cfg
3. 

Actual Results:
no --location=partition on bootloader

Expected Results:
bootloader ... --location=partition

Additional Information:

Comment 1 Jeremy Katz 2002-08-02 08:34:54 UTC

Fixed in CVS

Comment 2 Michael Fulbright 2002-12-20 17:38:25 UTC

Time tracking values updated

Comment 3 Mike McLean 2003-01-21 22:29:27 UTC

Just tested with Phoebe public beta 2.  While the installer does appear to have
installed the bootloader into the /boot partition, the anaconda-ks.cfg file has
the line:

bootloader --location=boot --append hdc=ide-scsi

Jeremy -  is 'boot' the correct location now, and not 'partition'?

Comment 4 Jeremy Katz 2003-01-23 03:22:06 UTC

Fixed in booty 0.18-1

Comment 5 Mike McLean 2003-01-30 18:30:52 UTC

fix verified