similar to: Configuration file not found when using non-standard installation path

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 Wed, Aug 27, 2014 at 2:08 AM, Prof. Dipl.-Ing. Klaus Knopper <syslinux at knopper.net> wrote: > Apparently, the rename of ldlinux.e32 to ldlinux.e64 for the 64bit > variant is already in the mainline git, so the only change left for > automatically chosing a different config file is the tiny patch attached > here, which will > > - prepend syslnx64.cfg to the config file

> Hello Ady & list, > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > >

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

Hello! I have outlined a proposal for a new feature of pxelinux in http://www.zytor.com/pipermail/syslinux/2004-December/004360.html (see the last couple of sentences) but nobody has commented it, so I am asking again: Imagine a company with a lot of departments and where network booting is widely used. Each department has different needs when it comes to operating systems. Because things

Hello, I wish to recompile only isolinux.bin and nothing else. I made some changes to core/fs/lib/loadconfig.c and now I wish to make (compile) isolinux.bin only. The only way how to do it seems to be "make" in the directory of syslinux sources. But this takes very long and compiles everything. Is there a better way to make only isolinux.bin? Something like "make isolinux"

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

Hello HPA, I have a request. Since v4.04, SYSLINUX supports one ".." in relative paths. It also supports multiple "../", only if the relative path ends with a specific directory, as in "../../otherdirectory/". Is it possible to expand this support to multiple "../" in SYSLINUX? BTW, ISOLINUX already supports this type of relative paths. The rest of

Hi, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO

> On Thu, 18 Dec, at 07:47:18PM, Ady wrote: > > I have a question about the PATH directive. In fact, the question is > > not about how it is currently working, but about its intention or goal, > > or how it was supposed to work (or how it was thought about for the > > 5.00 release). > > > > Previous discussions about the PATH directive in the Syslinux

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

I have a question about the PATH directive. In fact, the question is not about how it is currently working, but about its intention or goal, or how it was supposed to work (or how it was thought about for the 5.00 release). Previous discussions about the PATH directive in the Syslinux Mailing List, and its documentation (e.g. "PATH rules") left on me the impression that it was

On Thu, 18 Dec, at 07:47:18PM, Ady wrote: > I have a question about the PATH directive. In fact, the question is > not about how it is currently working, but about its intention or goal, > or how it was supposed to work (or how it was thought about for the > 5.00 release). > > Previous discussions about the PATH directive in the Syslinux Mailing > List, and its

Thank you for your reply. > On Fri, 02 Jan, at 02:23:48AM, Ady wrote: > > > > Hmm, I thought it was decided to consider the colon (":") character as > > deprecated, and instead we should be using a space character as > > separator for the PATH directive (or multiple lines). Well, at least as > > for the current MASTER HEAD, Syslinux 6.03. >

On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > So, my first (still incomplete and still inaccurate) attempt to write > some rules about the PATH directive, and ask about remaining doubts!... > > > The search (for c32 files) is supposed to respect the following rules: > > 1_ The search for c32 files is performed according to the following > rules. The search for

This one is the most critical for my app, but also possibly the most controversial to integrate. A few applications that convert isolinux ISOs to bootable USB, including mine, copy the ISO content to a VFAT formatted partition and then add syslinux to make it bootable. This would work great... if isolinux and syslinux shared the same defaults when it comes to configuration files.

> Their isolinux/isolinux.cfg has > DEFAULT loadconfig > LABEL loadconfig > CONFIG /arch/boot/syslinux/archiso.cfg > The file arch/boot/syslinux/archiso.cfg is readable too. > IIRC, Arch isolinux/isolinux.cfg should say: DEFAULT loadconfig LABEL loadconfig CONFIG /arch/boot/syslinux/archiso.cfg APPEND /arch/ Or it might be using relative paths: DEFAULT

On Fri, 02 Jan, at 02:23:48AM, Ady wrote: > > Hmm, I thought it was decided to consider the colon (":") character as > deprecated, and instead we should be using a space character as > separator for the PATH directive (or multiple lines). Well, at least as > for the current MASTER HEAD, Syslinux 6.03. Are you referring to commit 1945579 ("PATH: use a linked

> On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > > > So, my first (still incomplete and still inaccurate) attempt to write > > some rules about the PATH directive, and ask about remaining doubts!... > > > > > > The search (for c32 files) is supposed to respect the following rules: > > > > 1_ The search for c32 files is performed according to