similar to: [PATCH v2] Documentation: introduce the working directory

LDLINUX.SYS uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- This is a result of today's discussion of a previous patch ("Describe the --directory

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- syslinux accepts a --directory (or -d) option. As far as I can see this option only affects the installation location of the ldlinux.sys file. (It also affects the boot sector that syslinux generates, but that is not something user visible.) Currently man/syslinux.1 talks about the "SYSLINUX control files". That is not entirely

From: Gene Cumm <gene.cumm at gmail.com> SYSLINUX/COMBOOT: Abstract searchdir and fix the opendir call Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- First, change comboot.inc such that INT 22h AX=0020h (opendir) is about as simple and similar in behavior to INT 22h AX=0006h (openfile). Next, rename the function searchdir to searchdir4any, create a new function called

On Sun, Jan 6, 2019 at 12:58 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > > > This should have been the form for your desire as specifying the > > > >

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> > We would need at least: > > A_ the partitions and directory structure in which the following items > are _located_ : /dev/sda1: # tree . . ??? extlinux ? ??? ldlinux.c32 ? ??? ldlinux.sys ? ??? libcom32.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? menu.c32 ? ???

> On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > This should have been the form for your desire as specifying the > > > filename should have told it to create the BSS instead of writing it > > > to the VBR. Being the "fixed" HDD

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- man/extlinux.1 | 6 +++--- man/syslinux.1 | 10 +++------- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/man/extlinux.1 b/man/extlinux.1 index 3192122..62bf3b1 100644 --- a/man/extlinux.1 +++ b/man/extlinux.1 @@ -57,8 +57,8 @@ about your system and your BIOS; the vast majority of all problems reported turn out to

Folks, I've just pushed out another prerelease for the 5.00 branch. The idea behind this -pre was to merge in the final 4.06 release. I'm aiming for a final 5.00 release next week, but as we saw with the 4.06 branch, anything can happen and these deadlines can get pushed backwards. Please, test if you can. One thing that is going to happen next week is a Syslinux-6.00-pre1, which will

> syslinux[64].exe -i -f c: bootsecfile.bss > > This should have been the form for your desire as specifying the > filename should have told it to create the BSS instead of writing it > to the VBR. Being the "fixed" HDD instead of a removable drive like a > USB stick, "-f" is necessary. Hmm, instead? Could this syntax be some kind of unintended oversight?

Good afternoon all! I have a project I'm working on that requires Linux to be installed either to its own partition, or to the partition of a host OS (Windows or Linux). One way works, the other way does not... Use Case 1: In this scenario, Linux is installed to its *own* partition as is syslinux (syslinux -i /path/to/syslinux/files). Afterwards, I 'dd' the first 512bytes of that

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Fh, 0020h, 0021h and 0022h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Fh will return a valid value for all variants. INT22h, AX= 0020h, 0021h, and 0022h are only

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Eh, 001Fh, 0020h and 0021h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Eh will return a valid value for all variants. INT22h, AX= 001Fh, 0020h, and 0021h are only

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

Hi Peter, The main part of this pull request includes commits that try to replace as many __intcall() invocations as possible. Some remain, but not many (and eventually they'll be gone too). There's also a patch to make better use of ld's --as-needed option and various other bug fixes/cleanups. The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a: Only

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add get config full file name to SYSLINUX Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Returns the full configuration file name. Int 22h AX 001Eh for now as it appears that the COMBOOT API is designed to be strictly sequential. The API gets extended but only implemented (for now) for SYSLINUX in ldlinux.asm.

> On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > >> > > We would need at least: > > > > A_ the partitions and directory structure in which the following items > > are _located_ : > > /dev/sda1: > > # tree . > . > ??? extlinux > ? ??? ldlinux.c32 > ? ??? ldlinux.sys > ?

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add get current working directory call to most Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Adds an API call to obtain the current working directory. EXTLINUX will not return the correct value yet however SYSLINUX, ISOLINUX, and PXELINUX will return the correct value. For the moment, EXTLINUX will ONLY return

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

I have some concerns about the Syslinux boot process, which I'm now investigating in connection with my work on booting Live-CD images from USB flashdrives. Some of these are related to what seems to be inadequate documentation, but I think that there are also aspects of Syslinux operation which could be fairly easily improved. quoting from the official documentation: Since version 5.00,