|
Re: ks.cfg & RedHat tree: msg#00098linux.redhat.kickstart.general
On Sun, 28 Mar 2004, Fred Leeflang wrote: >Here's for the simple questions I have right now: > >- in (ISC) dhcpd.conf, should I just use > host <hostname> { > hardware ethernet xx:xx:xx:xx:xx:xx; > filename "/kickstart/<hostname>/ks.cfg"; > next-server 145.92.33.71; > } ? The filename and next-server settings are usually used for PXE - the location of the kickstart file is passed on the command line by the boot loader (PXELINUX, ISOLINUX etc.) >- what is the minimum contents of the ks.cfg that tells it > where to find /redhat/ES3.0 ? nfs --server nfsserver.example.com --dir /redhat/ES3.0 [/RedHat/{base,RPMS}] >- how do I debug the kickstart process on the client? > (ie. make it show which ks.cfg it's trying to get, > which NFS folder it's mounting etc.) Watch the syslog output on the server (/var/log/messages), watch the virtual consoles of the client (Alt+F2, Alt+F3 etc.) Cheers, Phil |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | ks.cfg & RedHat tree: 00098, Fred Leeflang |
|---|---|
| Next by Date: | RHEL AS-2.1 U3 extremely slow - nfs issue?: 00098, Jayaraman, Siva |
| Previous by Thread: | ks.cfg & RedHat treei: 00098, Fred Leeflang |
| Next by Thread: | Re: ks.cfg & RedHat tree: 00098, Fred Leeflang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |