Hi, On Tue, 2004-11-16 at 10:08 -0500, Jason Powers wrote: > > 5) In the /etc/dhcpd.conf file, it refers to "linux-install/pxelinux.0" as > > the PXE bootable image, but when the PXE client connects this file is not > > found. I copied /usr/lib/syslinux/pxelinux.0 (from syslinux RPM) to > > /tftpboot/linux-install. > > > > I changed this. Whatever is referred to as the pxelinux location is > actually tacked onto /tftpboot/. I'm concerned that parts of the program > may attempt to run and be looking inside /tftpboot/ for the images, or > be looking for non-pxe files realitve to that path. Anyway I changed it > to /pxelinux.0 and dropped the files in /tftpboot to make my life easier. So, you'd no /tftpboot/linux-install directory? Bah, I see where this stuff comes from now. system-config-netboot copies it over in a %post scriptlet. That's broken. > > 7) When I run "python statelessGenPXEConfig.py" after adding the MAC > > addresses, I get "Unable to get NFS location of DemoSystem snapshot > > DemoSystem-1". I'm not exactly sure where it's supposed to have picked up > > the NFS path definition from. It appears to me from browsing some of the > > code that somewhere along the line I was supposed to have executed > > "stateless-servers", but I didn't see anything about that in the > > documentation. > > > > In the config.py you can control all the paths the python scripts look > to. This need to be changed, I think, to run off the > etc/sysconfig/stateless file, because users aren't going to manipulate > python scripts (no matter how simple it may be). You shouldn't need to change anything in config.py. Cheers, Mark.
