Mark,
Check to see if you have syslinux installed. From my experience,
installing syslinux-2.04-2.i386.rpm and the making /tftpboot/pxelinux.cfg
directory manually works. What version of TFTPD are you using? I have had
the best luck using atftpd after uninstalling Red Hats TFTPD server( you
Can someone provide me the info to remove my email
address from the mailing list. Thanks.
=
Regards,
Sagar
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-
In response to Bas van der Viles: I'm running V3.0.X and am also going
to give a closer read to the web page you pointed me to at
http://www.fysik.dtu.dk/CAMP/Niflheim/systemimager.html which appears
to have a lot of good information.
In response to this note, I'm a little confused about netbo
ok, I'm getting even closer...
I tried running mkclientnetboot again and confirmed it had apparent
effect on systemimager.conf
I manually set the NET_BOOT_DEFAULT to 'local'
I restarted netbootmond
I did a new install onto one of my client nodes
I rebooted the client
It reported "Booting from loc
Mark,
Which version of systemimager do you use? Only version 3.X support this
systemimager.conf)
NET_BOOT_DEFAULT = local
If you have 2.X version (it also works for 3.x). There is software for
it:
ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz
There is a good d
Hi Mark,
/etc/systemimager/systemimager.conf
# This setting affects netbootmond. If set to LOCAL, then after successful
# completion of an install, a client's net boot configuration is modified to
# ensure future boots will happen from the client's local disk.
# NET_BOOT_DEFAULT can be set to lo
From my reading of the description of this on some web pages (the only
local documentation is to run the command with -help, but I'm sure
everyone already knows this) all I need to do is run the command
mkclientnetboot -all-clients
and whenever I do a brand new installation over the network, it
