Re: FC2 network kickstart not working

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 27, 2004 at 08:44:34AM -0500, Ken Teh wrote:
> I had the same problem until I switched to using DNS names for the server 
> both at the syslinux boot prompt, that is, for example,
 
> linux ks=nfs:fcserver.mynet:/disks/fc2/ks/bugs

> The symptoms were exactly as you described.  The DCHP part goes off
> without problems, but the installee never contacts the NFS server.  Hope
> this helps.  I'm guessing they changed anaconda.  Live and learn.

Hmm. I've just looked at the alt-f3 and see this:
* url is 192.168.8.2:/kickstart/
* file location: nfs://192.168.8.2:/kickstart/192.168.8.10-kickstart
* failed to mount nfs source

I tried modifying dhcpd.conf to specify a name but it just
turns it back into an IP address there and then. So I specified
ks=nfs://pxenfs.sbrk.co.uk:/kickstart/ on the boot command line
instead of just ks. On alt-f3 I see:
* url is pxenfs.sbrk.co.uk:/kickstart/
* file location: nfs://pxenfs.sbrk.co.uk:/kickstart/192.168.8.10-kickstart

Bingo! It works!

Thank you Ken.

Paul



[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux