Bug 6202 - kickstart ignores "next-server" definition in dhcpd.conf
kickstart ignores "next-server" definition in dhcpd.conf
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-10-21 18:24 EDT by Michael J. Carter
Modified: 2015-01-07 18:39 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-10-22 10:05:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael J. Carter 1999-10-21 18:24:55 EDT
When attempting a kickstart/DHCP/NFS install, the installer
attempts to mount the DHCP server instead of the machine
defined by the next-server in the dhcpd.conf:

The following dhcpd.conf stanza worked w/ RH6.0, but now
fails with the message "failed to mount" on the Alt+F3 console:

 group {
        filename "/root/kickstart/wyrd.node";

        host forte2 {
                hardware ethernet 00:a0:cc:56:1c:4a;
    } is the IP address of the dhcpd server.
Comment 1 Jay Turner 1999-10-22 10:05:59 EDT
*** This bug has been marked as a duplicate of 5589 ***

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