Paul Reilly wrote:
> I'm testing out PXELinux/SysLinux [1] to do a remote install
> over PXE with Kickstart.
I've got that working with both a customized Red Hat 7.3 and Whitebox 3.0.
> default linux
> label linux
> kernel vmlinuz
> append ksdevice=eth1 load_ramdisk=1 initrd=initrd.img \
> network ks=nfs:mymachine.tld:/linuxboot/ks.cfg
>> Does that look OK, or am I missing something?
Seems close enough to mine, though I've only ever done it through eth0...
LABEL whitebox-ide
KERNEL pxeboot.whitebox/vmlinuz
APPEND initrd=pxeboot.whitebox/initrd.img \
ks=nfs:192.168.167.254:/whitebox/nfs/kickstart/ide.cfg ksdevice=eth0
Don't be afraid to use ethereal to figure out what's going on. Could be
DNS. Could be the NFS server refusing the mount request (reverse DNS on
the client IP address can be important). Perhaps it is getting the
kickstart file, but not using it due to some option or other - check the
other ttys on the installer screen, maybe paste the kickstart file here.
It should be possible to snaffle the kickstart file through FTP, or HTTP
- with nothing more than the appropriate URL as the ks= setting.
Paul.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!