search for: dentifier

...ndings/ocaml/llvm/llvm_ocaml.c:19: In file included from /home/leila/llvm/bindings/ocaml/llvm/llvm_ocaml.c:19: C:\Objective Caml\lib/caml/alloc.h:34: warning: parameter names (without types) in function declaration /home/leila/llvm/bindings/ocaml/llvm/llvm_ocaml.c:524: error: (Each undeclared i dentifier is reported only once /home/leila/llvm/bindings/ocaml/llvm/llvm_ocaml.c:524: error: for each function it appears in.) I compile LLVM under my cygwin environment (x86), and it seems to link with ocaml lib in my C: filesystem in windows. That's a little wired. And I tried to specify the ocaml p...

...I'm not saying I'm right - but it's unofficially version 3. That's the firmware version. (I'm sure it's based on Intel's reference PXE implementations. All PXE ROMs seem to be.) My clients report 2.01 for their firmware version, when doing BIOS. i.e. Vendor Class Identifier == PXEClient:Arch:00000:UNDI:002001 And 3.16 when doing UEFI 64 bit. I.e., Vendor Class Identifier == PXEClient:Arch:0007:UNDI:003016 Spike

I'm looking for either a way of setting the root path - a Linux style "pivot_root" functionality, that would be perfect. Also a way of overriding prefixing the root path with a URL or some other acceptable syntax to designate to use a different TFTP server. That would really make PXELinux really versatile. Some people concerned about security may want a way of blocking that just

On Mon, Dec 29, 2014 at 04:15:56AM -0800, Patrick Masotta wrote: > On Mon, Dec 29, 2014 at 08:47:54AM +0100, Luke Ledgerd wrote: > > I think I'd like to ask for a feature request to allow pxechn.c32 > > to work with EFI too and to have the ability for PXELinux to have a > > ROOT path variable (kind of like gpxelinux.0) that can either have > > HTTP or TFTP urls.