Well.... I guess that is true. However when I setup my pxe environment I had to define a location for my ks.cfg (usually the same nfs share as my RedHat binaries) in my /tftp/pxelinux.cfg/default file.It would then mount and read my ks.cfg for the install parameters. Which included the NFS share of my RedHat binaries. You can create a ks.cfg file to do the interactive setup from the keyboard and monitor. James jdickson@xxxxxxxxxx On Fri, 2003-01-17 at 12:22, seth vidal wrote: > On Fri, 2003-01-17 at 13:20, Matthew Boeckman wrote: > > Hi list! > > > > This seems the most likely place to get an answer to my question, so > > I'll try here first. I've got a PXE server setup per the documentation, > > with all vmlinuz and initrd images in place. > > > > What I'm trying to do, is boot a PXE client, and install from it on > > monitor and keyboard. I have RedHat 7.3 on the PXE server, along with > > disk 1 and disk 2 exported via nfs. My main question is, do I have to > > have kickstart files in place as well? My assumption is that when I fire > > up the client, it will find DHCP, then find PXE server, and just output > > the regular "What type of install do you want" stuff to the PXE Client > > monitor. If that is correct, and I can just say nfs pxeserver:/mntpoint > > then I'm fine. If I need a kickstart file for PXE to work, I can do that > > too, just didn't really intend on going that way. > > > > > kickstart happens after syslinux boots. pxe happens well before that. > > So no - pxe and kickstart do not have any interdependencies. > > -sv > >
