In testing the current CVS version of OSCAR, which uses SystemImager
3.2.0, I have found a problem when booting the nodes for installation.

The clients will not build because the /tftpboot/pxelinux.cfg/default
file is incorrect, it's a "localboot" file, not the expected SI
kernel/initrd download file.  I manually copied
/etc/systemimager/pxelinux.cfg/syslinux.cfg to
/tftpboot/pxelinux.cfg/default; this allowed the client to boot and
build.

Is this a problem with SI 3.2.0 (more specifically,
systemimager-i386boot-standard-3.2.0-1)? I've verified the i386boot
package contents are correct.  An examination of
/etc/systemimager/pxelinux.cfg shows the default file is a copy of
syslinux.cfg.localboot.  Is this intended?

Alternatively, was there a modification to 3.2.0 that changed the
/etc/systemimager/pxelinux.cfg/default file from a kernel/initrd
download file to a localboot file?  Should
/etc/systemimager/pxelinux.cfg/default be ignored and
/etc/systemimager/pxelinux.cfg/syslinux.cfg be used instead?

-- 
David N. Lombard
 
My comments represent my opinions, not those of Intel Corporation.


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Sisuite-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to