similar to: PXE-Linux like default configuration file selection with syslinux?

Mattias Schlenker <ms at mattiasschlenker.de> wrote: > Is ifcpu.c32 or ifcpu64.c32 sufficient for your task? No. I need to detect a given machine by something unique. E.g. the MAC-address of the Ethernet Interface CPU-id or such, because I have custom kernels for all the machines. Sven -- If you can spend five minutes on the Internet and do not run Linux, you're a genius. (Dirk

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

Not much to it, but thought I'd offer. - Shao From c668e24421a344231fc3fba31a26c88e92d03f43 Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Tue, 2 Oct 2012 22:02:04 -0400 Subject: [PATCH] pxedump.c32: Simple PXE cached packet dumping Usage: pxedump.c32 --cached Mostly useful with a serial connection, to capture the lengthy output Signed-off-by: Shao

Hello, is it possible to select the default boot image by hardware properties? I corrently boot a couple of laptops fom a single USB stick and I would like to select the default kernel image automatically. Sven -- Trotz der zunehmenden Verbreitung von Linux erfreut sich der B?r, und - dank Knut - insbesondere der Eisb?r, deutlich gr??erer Beliebtheit als der Pinguin. (Gefunden bei

Yes, MENU HIDE would work as well, but still requires additional entries for each case (possible entries for pxe, syslinux, isolinux, cpu architectures, PCI devices, lua scripting scenarios, etc.) By blocking modules, I meant that as long as I disable user editing of menu commands via ALLOWOPTIONS 0, I cannot use any of the following com32 modules without creating duplicate LABEL entries for each

I did confirm earlier that this does work, and combined with a MENU HIDDEN to hide it from the visible menu it is a possible solution. I originally assumed that this was due to that going down a different code path and did not mention it, apologies. The scale of my menu makes doubling/tripling menu entries less ideal, though. Do we consider it intended functionality that modules such as whichsys

Hi I have a scenario where I need to test for whether I have booted via a syslinux ISO image in init-premount as opposed to (say) PXE boot. Is there any variable that I can test for this? thanks vk

On Sun, Sep 20, 2015 at 3:57 PM, syslinux-bot for Ady <ady-sf at hotmail.com> wrote: > Commit-ID: 7d9c9eca562857fed25b4c8ef902e3de968d7631 > Gitweb: http://www.syslinux.org/commit/7d9c9eca562857fed25b4c8ef902e3de968d7631 > Author: Ady <ady-sf at hotmail.com> > AuthorDate: Sun, 20 Sep 2015 15:35:52 -0400 > Committer: Gene Cumm <gene.cumm at gmail.com> >

On Thu, Sep 17, 2015 at 9:37 AM, Sven Geggus via Syslinux <syslinux at zytor.com> wrote: > Hello, > > when booting via pxelinux I can change the image to be booted based on > client uuid, and MAC-Adresses. > http://www.syslinux.org/wiki/index.php/PXELINUX#Configuration > > Now when using syslinux I would like to be able to also do this as I like to > use one usb

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

Hi there, ----- Original Message ----- From: koxudaxi at gmail.com To: syslinux at zytor.com Date: 01.04.2013 10:00:27 Subject: Re: [syslinux] Problem with pxelinux 5.0 and memtest > On 04/01/2013 09:28 AM, H. Peter Anvin wrote: >> On 03/31/2013 05:26 PM, Koudai Aono wrote: >>> I ran the test on a x86 emulator is called Oracle VirtualBox. >>> I think it might not be

Hi, ________________________________________ From: Gene Cumm <gene.cumm at gmail.com> Sent: Wednesday, March 16, 2016 00:56 To: Jan Frode J?ger Cc: syslinux at zytor.com Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: Without trying to figure out where data is

> > Is this "ArchLinux" entry equivalent to "\EFI\syslinux\syslinux.efi" > > in your UEFI firmware? > > Note: UEFI firmware is supposed to use (or show) backslash "\" as path > > separator. > > You have a great point there. > I redid the "efibootmgr" installation and instead of > > efibootmgr -c -d /dev/sdd -p 1 -l

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk

> > On 09/20/2013 02:34 AM, Ady wrote: > >> There might be an alternative (and possibly others too): let the user > >> select the appropriate firmware from within pxelinux.cfg/default. > >> > >> So, keep using the same method you used in previous versions, instead > >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >

On Mon, Mar 16, 2015 at 9:03 AM, Ady via Syslinux <syslinux at zytor.com> wrote: Hi Ady, > please next time use "Reply All" (instead of the simple "Reply") for the mailing list emails ... Sorry about that. Please add my reply to the list for me. Thanks. > Is this "ArchLinux" entry equivalent to "\EFI\syslinux\syslinux.efi" > in your UEFI

> More context to this: syslinux_run_command calls into load_kernel(), and somewhere behind load_kernel things break. This is also broken at the boot: console prompt. Any commands executed at the boot: prompt also lose all parameters. > > > With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). > > An

Hello, At the boot prompt ALLOWOPTIONS 0 is only applied to implicit kernels and not to labels. For configuration which want to allow selection, but prevent customization of the kernel command line, this behaviour is bad. Also the IMPLICIT 0 is applied to both the boot prompt and configuration setting (like DEFAULT); but one could argue that only the command supplied at the prompt make sense to

Hello, as said in the subject; I am having problems with ifcpu.c32 and ifcpu64.c32 detecting a Athlon II X4 CPU correctly as a 64Bit capable CPU. Ifcpu64.c32 does not detect PAE capabilities, also. Both boot the last (32Bit, non-PAE) entry. On two other Core2-based machines I have here, everything works. Can someone tell me what exactly these modules are looking for? Maybe I can compare that