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

Re: Attempting customized network install, including ks.cfg



On Fri, 7 Jun 2002, Frank McPherson wrote:

>BUT, I am still interested in debugging my current approach of referring
>to the kickstart config on the kernel boot options line, which is
>retrieved through pxe, in the form of ks=nfs:192.168.1.160/rh-7.2/ks.cfg
>or ks=http://192.168.1.160/rh-7.2/ks.cfg.

Phil's guide to debugging kickstart:

1. Attach a keyboard and screen to the victim.
2. Try kickstart
3. Flick madly between virtual consoles (Alt-F2, Alt-F3 etc.) whilst
looking for error messages.

Usually something useful pops up in one of them. In order, the problems
I usually encounter that make KS go interactive are:
- Can't mount NFS server
- Can't find kickstart file
- Can find kickstart file, but wrong directory specified (the KS file
must point to a directory which contains RedHat/RPMS and RedHat/base -
don't know about .isos)

This file works for me, as /tftpboot/pxelinux.cfg/default:

default ks
prompt 1
timeout 30
label ks
  kernel vmlinuz
  append ks=nfs:10.7.8.222:/vol/redhat/kickstart/ initrd=initrd.img lang= devfs=nomount ramdisk_size=8192

The "lang=" is important - anaconda goes interactive without it.

Cheers,

Phil





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