search for: bls1

On Fri, Aug 30, 2019 at 12:15 PM Erik Rull <erik.rull at rdsoftware.de> wrote: > Hello Greg, > > thanks a lot - I will try out your script next week. > I jut went through the script - there is a line containing: > bls1 include > > I would carefully assume that this line is only valid when patching > syslinux, > correct? What will happen if this is read by a non-patched syslinux? Will > it > cause errors or will it simply be ignored? > > That is correct. "bls1 include" would cause...

...ot Loader Specification". This patch enables syslinux to parse the drop-in files that are defined by this new specification. Link to documentation of the options added to syslinux by this patch: https://drive.google.com/uc?export=download&id=1nuRISVJeE1whYggFURywoQFpPzc6s1MC MD5 (syslinux-bls1.txt) = ad845afd302932edf505185b2966c10d Link to The Boot Loader Specification: https://systemd.io/BOOT_LOADER_SPECIFICATION Link to demonstration bootdisk image (82MB gzipped): https://drive.google.com/uc?export=download&id=1A9psiWfR7jK316DxMRkc5iMkQ-zhEHiG MD5 (syslinux-bls1.img.gz) = 963405...

I just created something very similar for one of my own projects. I have a disk image that you can "dd" onto a hard drive or USB drive and a bash script demonstrating how it was done here: https://www.syslinux.org/archives/2019-July/026476.html You don't actually need the patch for the dual BIOS/UEFI support. The patch in the above link is just to enable the reading of config

Gregory Bartholomew wrote: > That is correct. "bls1 include" would cause errors without the patch. The main > parts of the script that would be relevant to you would be the parts that create > the partition, set its type codes, write the first-stage boot loader to the > first 440 bytes of the disk, and lay out the file system (e.g. it...

...U register. From there, it is up to that 440 byte program to decipher the partition table. If you use syslinux's gptmbr.bin, you should be fine. On Sat, Aug 31, 2019 at 4:47 AM Erik Rull <erik.rull at rdsoftware.de> wrote: > Gregory Bartholomew wrote: > > That is correct. "bls1 include" would cause errors without the patch. > The main > > parts of the script that would be relevant to you would be the parts > that create > > the partition, set its type codes, write the first-stage boot loader to > the > > first 440 bytes of the disk, and lay...

Hello Greg, thanks a lot - I will try out your script next week. I jut went through the script - there is a line containing: bls1 include I would carefully assume that this line is only valid when patching syslinux, correct? What will happen if this is read by a non-patched syslinux? Will it cause errors or will it simply be ignored? Best regards, Erik Gregory Bartholomew wrote: > I just created something very similar...

...lor pwdheader 0 #ff808080 #ff000000 none menu color pwdentry 0 #ff808080 #ff000000 none menu color timeout_msg 0 #ff808080 #ff000000 none menu color timeout 0 #ff808080 #ff000000 none menu color msg04 0 #ff808080 #ff000000 none menu background #ff000000 menu resolution 800 600 menu title HAL 9000 bls1 include

...lor pwdheader 0 #ff808080 #ff000000 none menu color pwdentry 0 #ff808080 #ff000000 none menu color timeout_msg 0 #ff808080 #ff000000 none menu color timeout 0 #ff808080 #ff000000 none menu color msg04 0 #ff808080 #ff000000 none menu background #ff000000 menu resolution 800 600 menu title HAL 9000 bls1 include

Greetings Syslinux forum, I used this link; https://askubuntu.com/questions/1090891/grub-menu-colors and I followed it's tutorial for implementing the grub theme and was able to delete the menu border by creating a customized grub theme for UEFI boot (grub.cfg)! Do you know if the "syslinux.cfg"(legacy boot grub) can have it's border removed, like do you know if

...lor pwdheader 0 #ff808080 #ff000000 none menu color pwdentry 0 #ff808080 #ff000000 none menu color timeout_msg 0 #ff808080 #ff000000 none menu color timeout 0 #ff808080 #ff000000 none menu color msg04 0 #ff808080 #ff000000 none menu background #ff000000 menu resolution 800 600 menu title HAL 9000 bls1 include _______________________________________________ Syslinux mailing list Submissions to Syslinux at syslinux.org Unsubscribe or set options at: https://lists.syslinux.org/syslinux

...f (!fwd) + goto nomem; + + tmp = bwd; + for (i = len; i >= 0; i--) { + fwd[i] = *tmp; + tmp++; + } + free(bwd); + + return fwd; + +nomem: + dprintf("Out of memory error!\n"); + free(bwd); + free(fwd); + return NULL; +} + +static int parse_bls1_file(struct blsdata *bd, const char *filename) +{ + FILE *f = NULL; + char line[MAX_LINE], *p; + char *sort_field; + + dprintf("Opening bls entry: %s ", filename); + + f = fopen(filename, "r"); + dprintf("%s\n", f ? "ok" : "failed"...

...inux.org/archives/2019-July/026484.html I've also found Gregory's patch here: https://www.syslinux.org/archives/2019-July/026476.html If I understand this correctly, it doesn't fix the buggy strncat Gregory has mentioned - the patch adds support for another boot image format called BLS1 (now becoming popular). There's probably no point for me to try to apply this patch... I've also tried looking at the binaries available from Debian testing packages "pxelinux" and "syslinux-common"... and it seems to me that the "pxelinux" package only cont...