Bug 5830 - when installing nfs-server/directory isn't filled in automatically from pump data
Summary: when installing nfs-server/directory isn't filled in automatically from pump ...
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-10-11 14:14 UTC by Jonathan Peatfield
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-04-17 22:17:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

Description Jonathan Peatfield 1999-10-11 14:14:00 UTC 
Unlike earlier versions of the install code, the bootfile
information (and bootserver) information obtained by pump
isn't passed to fill in the nfs-server/directory fields in
nfsGetSetup() (or rather passed to it from mountNfsImage()
in loader.c).

pump certainly prints the bootFile string, but seems to do
nothing with it.  I'm not sure if the sa is being detected
or not and pump only seems to parse a small set of the
possible dhcp/bootp options...  Perhaps it should use Tag 17
(ROOT_PATH) rather than bootFile but there is more room in
bootFile as that doesn't go in the options space.

Sorry about putting this against pump but I can't find
anaconda (or install) on the component list.
Note You need to log in before you can comment on or make changes to this bug.