search for: hardcoded_opt

Displaying 3 results from an estimated 3 matches for "hardcoded_opt".

2014 Dec 09
0
Using of pxelinux configfiles for both BIOS and UEFI boot
...209 may solve this > if the ZENworks tftp server support this option with different values > depending on the architecture. Unfortuanelly til now I didn?t found out if > there is a support for this option. No need. Again, you have choices. http://www.syslinux.org/wiki/index.php/PXELINUX#Hardcoded_options -- -Gene
2014 Dec 08
4
Using of pxelinux configfiles for both BIOS and UEFI boot
Hello Gene, thank you for your answer > > - Is there a standard approach to use different vesamenu.c32 (and other architecture depending ) files in the pxelinux.cfg/default file depending on the boot architecture - especially for BIOS/Legacy and EFI64? > I'd say there's no standard but there are choices. Check out this page I wrote up. >
2014 Dec 11
2
Using of pxelinux configfiles for both BIOS and UEFI boot
...e ZENworks tftp server support this option with different values > > depending on the architecture. Unfortuanelly til now I didn?t found out if > > there is a support for this option. > > No need. Again, you have choices. > > http://www.syslinux.org/wiki/index.php/PXELINUX#Hardcoded_options > > -- > -Gene > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux I could be wrong about this, but... I think that it...