similar to: Module Versioning

On 02/24/16 20:45, Shao Miller via Syslinux wrote: > On 2/24/2016 22:55, Shao Miller wrote: >> Suppose...: >> - For non-releases: "git" + We take the first 6 chars of git commit >> - For releases: "ver" + major + "." + minor >> - For tar-balls: Something clever, maybe involving the date >> >> ...that we embed such a version in

On 2/24/2016 22:55, Shao Miller wrote: > Suppose... [...] > ...that we embed such a version in Syslinux core and in all OS > programs and modules. Maybe even with some nearby magic so that a > "whichver" command can examine and answer. > > If we have that, Ady's recent question is: If Syslinux' module-loader > encounters a module without version-info, do

What about using linux.c32?? It has some special initrd features, which someone has very kindly documented: ? http://www.syslinux.org/wiki/index.php?title=Linux.c32 Shao Miller Synthetel Corporation W: https://www.synthetel.com

Hi, I installed syslinux 6.0.3 on a UEFI/GPT system with Arch Linux. My /boot/EFI/syslinux/syslinux.cfg contains MENU SAVE but selected entries aren't saved. Just after I hit the Enter key in the syslinux menu, I see efi_adv_write: Unable to open file \ldlinux.sys, this message isn't displayed when the boot starts after the timeout (default entry). My installation didn't have this

Hello all. Here[1] is a branch where chain.c32 can chain-boot a partition on a GPT disk when given the partition index. boot: chain hd1 84 (For example.) - Shao Miller [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ chain_gpt

HiAnyone?Tal From: Tal Lubko via Syslinux <syslinux at zytor.com> To: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Saturday, March 26, 2016 11:39 PM Subject: [syslinux] Working with threads in c32 module Hello Everyone Is it possible to create threads in com32 module?I've searched and found "start_thread" function but I'm not sure if

On 10/13/2010 08:36 AM, syslinux-bot for Michal Soltys wrote: > Commit-ID: 9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Gitweb: http://syslinux.zytor.com/commit/9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Author: Michal Soltys <soltys at ziu.info> > AuthorDate: Wed, 13 Oct 2010 10:57:36 +0200 > Committer: Michal Soltys <soltys at ziu.info> > CommitDate: Wed, 13

Attached are 4 patches against Syslinux 4.06 providing two new options for the linux.c32 ComBoot32 module. If we are shifting gears towards 4.10 or 5 any time soon, feel free to let me know and I'll attempt to apply the patches to those and to deal with any conflicts. You can merge these commits onto your 4.06 from my 'multi_initrd' branch at:

Hi all, I need the Com32 binary so I can use it on my project. Or, maybe anyone can make the COM32 library as a single API file so I can easly call it after my .c32 is running?

On 2/24/2016 22:55, Shao Miller wrote: > Suppose...: > - For non-releases: "git" + We take the first 6 chars of git commit > - For releases: "ver" + major + "." + minor > - For tar-balls: Something clever, maybe involving the date > > ...that we embed such a version in Syslinux core and in all OS programs > and modules. Maybe even with some

I see there's a memtest on the Linux discs I've created... would it be possible to put another program in place (a module, perhaps?) that can calculate a hash using a certain algorithm (i.e. SHA512 or similar) to validate and print out the hash of the boot ISO before booting it? The integrity of the ISO is absolutely critical. Thanks, Bret

On 03/02/16 16:19, Ady via Syslinux wrote: > > That's not what common users are forced to deal with. Syslinux's binary > files in the wild come from different sources (official upstream > Syslinux, distros' packages, others). > > Since v.6+ (and possibly, even before it) a re-build might show some > inconsistencies between "the same version" of

Not much to it, but thought I'd offer. - Shao From c668e24421a344231fc3fba31a26c88e92d03f43 Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Tue, 2 Oct 2012 22:02:04 -0400 Subject: [PATCH] pxedump.c32: Simple PXE cached packet dumping Usage: pxedump.c32 --cached Mostly useful with a serial connection, to capture the lengthy output Signed-off-by: Shao

> On 02/24/16 20:45, Shao Miller via Syslinux wrote: > > On 2/24/2016 22:55, Shao Miller wrote: > >> Suppose...: > >> - For non-releases: "git" + We take the first 6 chars of git commit > >> - For releases: "ver" + major + "." + minor > >> - For tar-balls: Something clever, maybe involving the date > >> >

Even though Doug's out of the office, I'm submitting a patch to the ifcpu[|64].c32 COMBOOT32 modules for testing. Also available for perusal with a web browser at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=cc70d0fa5 5e35fabf250f4dccbaed2fa44f56da7 - Shao Miller --- >From cc70d0fa55e35fabf250f4dccbaed2fa44f56da7 Mon Sep 17 00:00:00 2001 From: Shao

Good day, Tal. Perhaps if you describe a little bit more about the rationale behind this single-file requirement, someone might be able to make an alternative suggestion that you haven't thought of. The BIOS- and disk-based Syslinux bootstrapping actually often has a filesystem-specific piece of code that lives in the filesystem's meta-data, as well as the primary file and COMBOOT32

On 2016.03.07 01:21, Shao Miller via Syslinux wrote: > 3. Disable the Microsoft precision warning, since Syslinux does lots of > this sort of thing. > > That last option seems pretty simple, without moving entirely from /W3 > to /W2. Could that work? (C4242) Unfortunately, there are some warnings that Microsoft, in their great wisdom, decided that driver developers should not

Chainloading a Linux system with syslinux fails unexpectedly with the lines: WARN: No MBR magic, treating disk as raw. ERR: Unable to find requested disk / partition combination. boot: coming after the usual lines SyslinuxBOOT .... (in UEFI menu) linuxBLFS (in syslinux menu) SUMMARY (additional gory details available upon request) ~~~~~~~~~

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

Hi all, I have a similar issue with Thomas Mieslinger mentioned in the previous mail. The difference is here isolinux is used instead of gpxelinux.0. I use isolinux 3.85, and "chain.c32 hd0" to boot the local Debian Lenny Linux on VMWare workstation 6.5, it fails. If I replace it with isolinux 3.84, it works. Hope this report helps. Steven. -- Steven Shiau <steven _at_ nchc org