Bug 10701 - kickstart AND no "next server" in DHCP
Summary: kickstart AND no "next server" in DHCP
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-04-10 15:56 UTC by Derrien
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-04-14 19:00:35 UTC
Embargoed:

Attachments (Terms of Use)

Description Derrien 2000-04-10 15:56:11 UTC 
When there is no "next server" in the DHCP reply (our DHCP server Sun
Solaris seems to ignore this fields !) in kickstart installation, kickstart
tries to use 0.0.0.0 for file server.
Comment 1 Erik Troan 2000-06-16 15:20:16 UTC 
What should it do instead?
Comment 2 Derrien 2000-06-16 15:33:37 UTC 
From redhat-6.2/i386/doc/ref-guide/s1-kickstart2-howuse.htm :
Note that if you don't specify a server name, then the client system will
attempt to use the server that answered the BOOTP/DHCP request as its NFS server

It seems odd to try to use the server 0.0.0.0 no ?
Note You need to log in before you can comment on or make changes to this bug.