similar to: syslinux, raid 1, and metadata 1.2

On Fri, Aug 4, 2017 at 12:06 PM, ian_bruce--- via Syslinux <syslinux at zytor.com> wrote: > 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 >

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,

On Wed, Jan 3, 2018 at 2:38 AM, Avi Deitcher <avi at deitcher.net> wrote: > Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in > the loop. Appreciated. > >> > which appears to be included in diskstart.inc. I will have to dig in and >> > see >> > how this all gets compiled (pointers always appreciated :-) ). >>

> You are thinking GRUB-like, among (too) many others. Heh, at least I am in good company. > A "sector" is not necessarily 512-bytes long. Fair enough, e.g. Advanced Format 4k sector disks. > The VBR, or Volume Boot Record, is not necessarily 512-bytes long. > Also, the VBR doesn't need to be restricted to the first sector of the volume alone. The "Design"

For reasons I won't get into, I need to use grub (not grub4dos, super grub, or any other variant) as multiboot loader on a USB thumb drive, but I also need some of the partitions to contain bootable content from syslinux-based ISOs. All of these syslinux partitions must be logical rather than primary partitions and they will not be the first partition on the drive. Porting the syslinux

On Tue, Jan 2, 2018 at 1:03 PM, Avi Deitcher <avi at deitcher.net> wrote: > Thanks for the response, Gene. Much appreciated. I didn't get all of it; > mind if I follow on below? > >> ldlinux.sys is ldlinux.bin without the VBR (Volume Boot Record) code. > > Makes sense. > >> > 1. Where is the code that goes in the VBR or Block Group 0 padding? >>

Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in the loop. Appreciated. > which appears to be included in diskstart.inc. I will have to dig in and > see > > how this all gets compiled (pointers always appreciated :-) ). > > Yes. > Is the build process documented? Or am I just going to have to plod through the makefiles? > As Ady said,

On Sat, Jan 6, 2018 at 12:34 PM, Avi Deitcher <avi at deitcher.net> wrote: >> > Is the build process documented? Or am I just going to have to plod >> > through >> > the makefiles? >> >> I don't think so. > Oh well... >> > 1. Run installer >> > 2. Installer loads ldlinux.sys onto the filesystem (and copies >> >

On Mon, Jan 1, 2018 at 11:06 AM, Avi Deitcher via Syslinux <syslinux at zytor.com> wrote: > Hi Syslinuxers, > > I am trying to understand the basic load chain in fat32 and ext4. I dug > into the assembly for MBR, which is pretty straightforward: > > 1. Find boot partition (or use the pre-defined one at byte 440 for > altmbr.bin) > 2. Load the first 512-byte sector of

Hello Ady, On Wed, Aug 27, 2014 at 10:52:25AM +0300, Ady wrote: > > 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 >

> > > Is the build process documented? Or am I just going to have to plod > through > > the makefiles? > > I don't think so. > Oh well... > > 1. Run installer > > 2. Installer loads ldlinux.sys onto the filesystem (and copies > ldlinux.c32, > > but irrelevant for now). > > 3. Installer calculates which blocks in the filesystem contain

> > E_ Under FreeDOS, SYSLINUX.COM doesn't seem to install ldlinux.* > > (specially when used with "--directory"), and there are no ([error]) > > messages; not even when executed with no parameters, or with > > "--help", or with "--version". The messages disappeared _after_ > > 5.00-pre7. > > Right, as Peter pointed out on

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 > > > >

Before I reply on-topic, I'd like to request from people participating in this public mailing list to _avoid_ top-posting whenever possible, and when replying, please quote what's relevant only. Now, back to the topic. > " > Booting... > Error loading operating system_ > " > at the bottom of screen and hangs. I can only reboot using ctrl-alt-del. AFAIR,

A proposal for changing the LDLINUX.SYS layout and flow: The current situation ("old style"): ldlinux.bin's physical layout: - VBR - 512 bytes of padding (never lands in memory) - ldlinux.sys, which is: - Sect1 code (494 bytes, leaving enough room for at least one extent, as planned) - Extent pointer patch space (1920 bytes) - The rest of the code

Sorry for the late response. I am set to digest on this list. One of my chief complaints about mailman (besides non-searchable archives), is that you can either get every message or digest, but not "digest except for threads to which I have responded for which I want every message directly". > The command line installers have the core module and the bootloader file, all embedded

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

Hi Syslinuxers, I am trying to understand the basic load chain in fat32 and ext4. I dug into the assembly for MBR, which is pretty straightforward: 1. Find boot partition (or use the pre-defined one at byte 440 for altmbr.bin) 2. Load the first 512-byte sector of the partition (VBR for fat32, Block Group 0 padding for ext). 3. Execute that code The code that is loaded, however, has to be too

Thanks for the response, Gene. Much appreciated. I didn't get all of it; mind if I follow on below? ldlinux.sys is ldlinux.bin without the VBR (Volume Boot Record) code. > Makes sense. > > 1. Where is the code that goes in the VBR or Block Group 0 padding? > > diskboot.inc. > which appears to be included in diskstart.inc. I will have to dig in and see how this all gets

On Tue, Dec 20, 2016 at 7:14 AM, piranna--- via Syslinux <syslinux at zytor.com> wrote: > I'm trying to install SysLinux on a disk image as part of NodeOS > automated build process, but seems SysLinux requires administrative > priviledges. I suposse this is needed because `syslinux` command try > to mount the disk image / device to store the needed files, that > otherwise