Bug 5605 - Kickstart, NFS, and --bootproto static
Kickstart, NFS, and --bootproto static
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-10-05 17:41 EDT by matt.samsonoff
Modified: 2008-05-01 11:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-11 14:58:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description matt.samsonoff 1999-10-05 17:41:21 EDT
If you use ks=floppy with NFS, the loader configures
networking via DHCP and ignores the network config in the
kickstart file.

This fails horribly on my network because the addresses in
the DHCP pool don't have names (I don't know why -- not my
DHCP or DNS server) and the NFS server doesn't like to serve
clients without host names. I'm trying to use --bootproto
static so I can assign a static IP address that has a proper
host name to each client machine and avoid the NFS server's
objections.

Check out the code near anaconda/loader/net.c:511 which
reads something like this:

>  if (!bootProto)
>    bootProto = "dhcp";
>
>  if (!bootProto) {
>    if (ksGetCommand ...
>      :
>      : /* reads ks.cfg network info */
>      :

Yikes.
Comment 1 Jay Turner 1999-10-20 15:25:59 EDT
This issue has been forwarded to a developer for further action.
Comment 2 cavanaug 1999-10-21 04:25:59 EDT
I have this problem as well and its *really* annoying. It is severely
holding up a larger scale deployment of Linux within our division.

I will be willing to test any fixes to this on a moments notice.
Just send me a new bootnet.img file.  --John C
Comment 3 Shawn M. Green 1999-12-17 23:55:59 EST
I'm having a similar, yet altogether different problem.  When doing a netboot
with the ks=floppy, I am specifying a static IP in the ks.cfg file.  The thing
is that is still hits my dhcp server and tries to continue that way.  Needless
to say, it's not joyous in the least.

Sigh...just one of the many bugs that I'm finding in kickstart.  Just need to
figure out the rest of them now.  :)
Comment 4 Jay Turner 2000-02-11 14:57:59 EST
This issue is resolved in the latest installer available in beta.

Note You need to log in before you can comment on or make changes to this bug.