similar to: PATH directive

Displaying 20 results from an estimated 90000 matches similar to: "PATH directive"

2014 Dec 19
0
PATH directive
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
2014 Dec 19
3
PATH directive
> 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
2015 Jan 01
0
PATH directive
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
2015 Jan 02
2
PATH directive
> 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
2015 Jan 13
0
PATH directive
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
2015 Jan 13
1
PATH directive
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. >
2016 Jun 10
1
When is PATH directive used?
Ady asked: > Have you read the "See also" section(s) of the wiki page(s)? Yes. > By reading the relevant wiki pages, a user should (_hopefully_) get to > the conclusion that the PATH directive is relevant for c32 modules, and > not a replacement for the CONFIG / INCLUDE directives nor for relative > paths based on the "Working Directory". There's nothing
2016 Jun 10
1
When is PATH directive used?
With 6.03, I'm trying the "common directory distinct config" approach from http://www.syslinux.org/wiki/index.php?title=PXELINUX-Multi-Arch which essentially sets a different PATH (for BIOS vs EFI64). It seems PATH is correctly used to load .c32 modules, but not to load 'memdisk': PATH syslinux/bios UI vesamenu.c32 <-- WORKS (tries /vesamenu.c32, 404 error,
2015 Aug 22
1
Configuration file not found when using non-standard installation path
Installing with: syslinux --directory otherdir -i my_unmounted_device will install the bootloader in the desired directory ("otherdir") under the root directory of the desired unmounted device ("my_unmounted_device"). All the corresponding syslinux-related files are located in the same installation directory. When booting this device, SYSLINUX fails to find a
2018 Dec 06
1
fixing debian's hd-media image
On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version
2014 Aug 01
5
syslinux efi configuration file name proposal
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 syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:
2017 Mar 06
2
config_cwd can be killed?
I asked before about config_cwd and after some more digging, it looks like it could be removed... Specifically, the documentation http://www.syslinux.org/wiki/index.php?title=Config#CONFIG says: ---------- * CONFIG config_file [new_WD] Load a new configuration file. The new configuration file is read, the Working Directory is optionally changed (if specified via an optional second parameter),
2017 Mar 06
3
PATH directive searches in reverse order with wrong separator
I've been trying to get syslinux.efi working in my environment again... Found what look like a bunch of little bugs that are very frustrating... First, the documentation on the Wiki says that as of 5.11, the list separator is space, not colon. But I can find no evidence that 5.11 was ever officially released or that a commit to git was made to make this change. 6.00 and following still use
2013 Jan 27
1
PATH directive rules
Hello Syslinux Team, If I understand correctly (and I should emphasize that condition), the lib*.c32 library modules, when required, are initially searched-for according to the following (fallback) rules: 1_ Search for the relevant lib*.c32 file(s) in the Current Working Directory. 2_ Search for the relevant lib*.c32 file(s) in the directory where ldlinux.c32 is located. Then the lib*.c32
2014 Apr 23
3
*.c32 for efi64 and efi32?
On 2014/4/23 ?? 12:54, Ady wrote: > Is this about not liking the need for (sub)directories (depending on > firmware)? Or is it about functionality? > > If I understood correctly the prior email threads, the (real) problem > was in trying to maintain the searching for: > > pxelinux.cfg/01-88-99-aa-bb-cc-dd > pxelinux.cfg/C000025B > pxelinux.cfg/C000025 >
2015 Jan 18
2
Error loading vesamenu.c32
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 18/01/15 a las 13:18, Gene Cumm escribi?: > On Sun, Jan 18, 2015 at 6:44 AM, Angel <angelv64 at gmail.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> Hello. >> >> I'm trying to setup an multiboot USB, mainly to install Debian >> using netinst images. >> >>
2014 Aug 01
0
syslinux efi configuration file name proposal
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 syslinux.efi to bootx64.efi and to >
2012 Nov 28
3
config.c32 fails in 5.00pre11
The config.c32 module (and the CONFIG directive) is not behaving as expected when using syslinux.exe 5.00pre11 as installer. To replicate: 1_ The content of the device: /dira /cat.c32 /config.c32 /ldlinux.c32 /ldlinux.sys /libcom32.c32 /pwd.c32 /syslinux.cfg /dira/dira.cfg 2_ Content of /syslinux.cfg: DEFAULT pwd1 PROMPT 0 LABEL config1 COM32 config.c32 /dira/dira.cfg APPEND /dira/ LABEL
2014 Aug 02
0
syslinux efi configuration file name proposal
Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for
2015 Jan 18
0
Error loading vesamenu.c32
> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory is relevant, specially for relative