similar to: DHCP option 93 for UEFI

Ady, There are at least 3 ways to set up your DHCP server to differentiate between std DHCP, BIOS PXE and UEFI PXE. Option 93 (arch) is one way. In ISC syntax, here's 3 ways: 1. Match on VCI class "pxe-clients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; set vendor-string = substring ( option vendor-class-identifier, 0, 9);

>>> Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. <<< ""exponential-like decay of IO rate"" could you please post a link on

This document: http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml Has the same (plus expanded) list of cpu arch values for parameter 0x93. This list matches RFC 4578 except for values 7 and 9 which are EFI ByteCode and x86-64. Turns out RFC 4578 is wrong https://www.rfc-editor.org/errata_search.php?rfc=4578 And 00:07 *is* the correct value for 64-bit x86 clients and the

In another mail I discussed my adventures on netbooting syslinux 6.03 and newer from iPXE, either from an emulated rom on qemu/kvm/ovmf or by chainloading via ipxe.efi onto a real HP Proliant DL360 gen9 piece of iron. You might have asked yourself, why chainload? Why not load it directly? Believe me, i tried. First I had to 'fix' my dhcpd.conf because HP probably read the docs on

On 07-08-15 05:56, Ady via Syslinux wrote: > If we are talking about UEFI x86_64, then the c32 files are all those > located under the "efi64" directory tree of the Syslinux build. Plus, > the relevant "ldlinux.*" core module. I wonder why ldlinux.c32 got renamed to ldlinux.e64 whereas all other modules remained their c32 extension. This confused me as a beginner.

>Several points (please read the whole email before doing anything else): > >1_ It is not clear whether you still need/want to "avoid displaying" the menu border (i.e. make it transparent). You mentioned that you >eventually managed to do so, but then you also ask (again) about vesamenu.c regarding the menu border. Or, perhaps... Do you >actually, really, want to

On Sun, Oct 6, 2013 at 8:21 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > C:\Program Files (x86)\Microsoft Visual Studio > 11.0\VC\include\concrt.h(313): warning C4530: C++ exception handler used, > but unwind semantics are not enabled. Specify /EHsc > (C:\lld-x86_64_win7\lld-x86_**64-win7\llvm.src\tools\lld\** >

The config.c32 module (and the CONFIG directive) is not behaving as expected when using syslinux.exe 5.00pre11 as installer. To replicate: 1_ The content of the device: /dira /cat.c32 /config.c32 /ldlinux.c32 /ldlinux.sys /libcom32.c32 /pwd.c32 /syslinux.cfg /dira/dira.cfg 2_ Content of /syslinux.cfg: DEFAULT pwd1 PROMPT 0 LABEL config1 COM32 config.c32 /dira/dira.cfg APPEND /dira/ LABEL

Hello dear list, Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. So it was time for the next step. Migrate this setup to our automated testing environment that runs

I have some questions about "ALLOWOPTIONS 0". [quote] ALLOWOPTIONS flag_val If flag_val is 0, the user is not allowed to specify any arguments on the kernel command line. The only options recognized are those specified in an APPEND) statement. The default is 1. [/quote] My understanding of the behavior of "ALLOWOPTIONS 0" is that unless I type-in a command that is exactly

> On 07-08-15 05:56, Ady via Syslinux wrote: > > If we are talking about UEFI x86_64, then the c32 files are all those > > located under the "efi64" directory tree of the Syslinux build. Plus, > > the relevant "ldlinux.*" core module. > > I wonder why ldlinux.c32 got renamed to ldlinux.e64 whereas all other > modules remained their c32 extension.

My summary: reviewing ALLOWOPTIONS found reasons for further reviewing 'ALLOWOPTIONS' Op 2014-07-12 om 04:35 schreef Ady: > > > I have some questions about "ALLOWOPTIONS 0". > > > > [quote] > > ALLOWOPTIONS flag_val > > If flag_val is 0, the user is not allowed to specify any arguments on > > the kernel command line. The only

> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory is relevant, specially for relative

Hi all, this is my first post on this list, hope someone can help me. I have to run a dhcp server on CentOS release 5.5 (Final). # yum list| grep -i dhcp dhcp.x86_64 12:3.0.5-23.el5 installed dhcp-devel.x86_64 12:3.0.5-23.el5 installed dhcpv6-client.x86_64 1.0.10-18.el5 installed after starting the dhcpd daemon, the windows Clients on the subnet (192.168.100.0/24) tells me, that there is no

I see what he is saying now. When you assign a click event with the Event.observe it does not allow you to call it with the $(''xxx'').onclick(); command as it''s looking for the onclick tag in the a tag. I''m stumped on a way to get this to work. Jon Whitcraft Web Application Developer Online Services - Indianapolis Motor Speedway (317) 492-8623

Hello. I'm testing version 4.06-pre5. Using the CONFIG + APPEND directive with RELATIVE paths and changing the base directory is sometimes failing. Booting with ISOLINUX is OK but SYSLINUX is not. To demonstrate an example, I have uploaded a little 7z archive containing: _ a little ISO image; _ a 1440KiB floppy image. Both images have the same directory tree and cfg files. The only

The following are some comments about Syslinux documentation as present in version 4.06 - 5.00pre9. 1_ In "./NEWS", the changelog for version 4.04 includes "GCC 4.5 fixes". Maybe the changelog for Syslinux 4.06 should include "GCC 4.7 fixes" (or 4.7.x ?). 2_ In "./NEWS", the changelog for version 4.05 includes "ISOLINUX: remove the .img file

> On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote: > > Am 27.06.2013 22:08, schrieb Matt Fleming: > > > I'm planning on releasing 6.01 next week. The list of changes (so far) > > > are appended below. This is going to be a quick bug fix release, mainly > > > because of the rather embarrassing bug in the 6.00 that prevents booting > > > a Linux

> > SYSLINUX 6.03 CHS 6.03-pre1 ... > > Failed to load ldlinux.c32 > Boot failed: please change disks and press a key to continue. > First, let me clarify that all the scripts and procedures in the Clonezilla site are not related to this official Syslinux mailing list or to The Syslinux Project. They are done by the Clonezilla team. Now that I know you are working

> I have some questions about "ALLOWOPTIONS 0". > > [quote] > ALLOWOPTIONS flag_val > If flag_val is 0, the user is not allowed to specify any arguments on > the kernel command line. The only options recognized are those > specified in an APPEND) statement. The default is 1. > [/quote] > > My understanding of the behavior of "ALLOWOPTIONS 0"