similar to: pxechn.c32 for EFI

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

In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to use pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE script. The relevant portion of my PXELinux config looks like this: LABEL MDT MENU LABEL ^B - MDT 2012 SP1 com32 pxechn.c32 APPEND undionly.kpxe -o 67.s=ipxe/mdt.ipxe However iPXE doesn't seem to get the option correctly, it goes into

On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > <blanalex at gmail.com> wrote: > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to > use > > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > > script. > > > > The

Hi, I am a new Ubuntu user and I am trying to get rid of Windows from all my computers forever! The only hurdle is my medical billing software Kareo. When I tried to run the exe file it states that it is extracting an MSI file and then shut out. I tried extracting the msi files running w/ the wine msi switch but it states that the msi file cannot run w/o the setup file. The program can be freely

> Does the EFI version of PXELinux support http like gpxe, that would be awesome loading down those 400 meg wim Windows PE File and loading them using wimboot from ipxe (that works still with PXELinux) - only I only got it working so far with tftp that makes no difference ;) Good question. I've only ever used tftp to first load vmlinuz/initrd and then ks.cfg. Then use HTTP for subsequent

On 06/16/2014 05:14 PM, Gene Cumm wrote: > This sounds like you're using gpxelinux.0 4.07 which as I stated will > introduce issues. Instead of using gpxelinux.0 4.07, try pxelinux.0 > 4.07 then do your chainload to lpxelinux.0 6.02. If this doesn't > solve it, try 6.03-pre14. When I DHCP boot to lpxelinux.0 6.02, and then pxechn.c32 back to lpxelinux.0 6.02 with the http

On Mon, Dec 29, 2014 at 8:16 AM, Geert Stappers <stappers at stappers.nl> wrote: > 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

Spike White, Sent: Saturday, December 27, 2014 4:32 AM > > Luke, I have considerable experience with this. We use WDS at work > for PXE (MS-centric shop). I use pxelinux at home. > > I've got WDS working in our test lab w/ UEFI. As you state, it strongly > wishes to do proxyDHCP (port 4011). More on this in a bit. > > It's quite common to segregate the DHCP

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no

> 1) SYSLINUX on EFI must be extended to load arbitrary > EFI binaries > (perhaps through a module first > like how linux.c32's code became the > Linux loader). Do you know 6.03 status on this topic? i.e. can something like bootmgfw.efi be booted today or not? Pat

Hey guys, We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off anything you want to including PXELinux. The stuff I was talking about before with PXELinux not working in

On 07/03/2014 08:44 PM, Gene Cumm wrote: > On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis wrote: > >> I suppose we could try making an ISOLINUX CD for the local boot, which then >> uses pxechn.c32 to connect to our PXE server? > > pxechn.c32 requires a functional PXELINUX. If I understand the issue correctly, is it that pxelinux.0 does not have a network stack and

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;

>>> 1) SYSLINUX on EFI must be extended to load arbitrary >>> EFI binaries >>> (perhaps through a module first >>> like how linux.c32's code became the >>> Linux loader). >> >> Do you know 6.03 status on this topic? >> i.e. can something like bootmgfw.efi be booted today ornot? > http://bugzilla.syslinux.org/show_bug.cgi?id=17

On Dec 30, 2014 6:06 AM, "Patrick Masotta" <masottaus at yahoo.com> wrote: > > > > 1) SYSLINUX on EFI must be extended to load arbitrary > > EFI binaries > > (perhaps through a module first > > like how linux.c32's code became the > > Linux loader). > > Do you know 6.03 status on this topic? > i.e. can something like bootmgfw.efi be

Adding an option for initrdfile= boot argument to be ignored by wimboot worked just fine. They can add this patch, which is probably most sane, or syslinux could add the INITRDFILE configuration option instead of having to append the option for linux.c32 wimboot-2.4.0/src/cmdline.c @ Line ~107 } else if ( key == cmdline ) { /* Ignore unknown initial

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off

On 06/16/2014 10:41 AM, Gene Cumm wrote: > [...] Initially I wrote pxechn.c32 to allow further > modifications of the DHCP data [...] Awesome! In fact, this might allow us to install an automatic 'http' prefix on all subsequent requests, to avoid slow tftp --- or is that a bad idea, and/or is there a way to default all transfers to http without using pxechn and without prefixing

Hi All, I've been trying to understand how to use pxechn.c32 to chain a local pxelinux menu item to a remote server which has it's own pxelinux hierarchy served via TFTP and HTTP. We have no control over DHCP next-server and filename fields so I wanted to exploit the "prefix" -p option that pxechn.c32 accepts. I spent a long time hitting my head against a brick wall until I