Bug #23404

Deploy latest PXElinux files

Added by Arend Lapere over 2 years ago. Updated 4 months ago.

Foreman modules
Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


As I set-up my foreman installation to boot WinPE, over wimboot, utilizing wimboot I've noticed this only seems to work with syslinux >= 5 (I've tested it with the latest syslinux and works like a charm).
However, currently these files get overwritten after running foreman-installer; even more, not all files are automatically deployed. This is currently the list of files I've deployed to my TFTP proxy in order for wimboot to work:
- ldlinux.c32
- libcom32.c32
- libutil.c32
- linux.c32
- menu.c32
- pxelinux.0

Would be nice if we could actually use the latest syslinux (at the time of writing this is v6) and deploy the files mentioned above automatically. This would at least reduce some of the burden of setting up wimaging manually.


#1 Updated by Lukas Zapletal over 2 years ago

  • Category deleted (TFTP)
  • Project changed from Smart Proxy to Installer

Hello, our installer copies minimum set files from OS installed syslinux. Flipping to the installer team.

#2 Updated by Arend Lapere almost 2 years ago

  • Triaged set to No

In addition to this, if we upgrade syslinux, we should use the new lpxelinux.0 kernel as a default; as this provides us with the ability to load files over HTTP. Again, for windows deployments this is very much the wanted path, as this allows us to easily fetch the peSetup.cmd file.

#3 Updated by Tomer Brisker almost 2 years ago

  • Target version deleted (1.17.0)

#4 Updated by Ewoud Kohl van Wijngaarden 4 months ago

  • Triaged changed from No to Yes
  • Category set to Foreman modules

At least on CentOS 7 these files are not present by default. That means we can't do this for all platforms now.

The actual code is at in case you want to fix it yourself.

Also available in: Atom PDF