similar to: PXELINUX Tboot

On Fri, 5 Dec 2014, Gene Cumm wrote: > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. It can then use disc access (not PXE), or you can pass it the ?real? kernel, but also e.g. configuration files, as Multiboot

On Fri, Dec 05, 2014 at 10:16:10AM +0100, Thorsten Glaser wrote: > On Fri, 5 Dec 2014, Gene Cumm wrote: > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > I???m not permitted to edit either that page or its talk page. > Do I submit the content addition here, then? Euh, yes, that is an option. Hereby I volunteer for updating the wiki with updates that get to

On Sat, Oct 10, 2015 at 03:10:26PM +0300, Ady via Syslinux wrote: > From: Geert Stappers <stappers at nero.gpm.stappers.nl> > > > > com32/mboot/map.c: removed trailing spaces > > > > They were introduced by the patch for ELF64 support. > > > IMHO, the trivial trailing-space cleanup could be included in the same > commit too, instead of adding an

From: Geert Stappers <stappers at nero.gpm.stappers.nl> They were introduced by the patch for ELF64 support. --- com32/mboot/map.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/com32/mboot/map.c b/com32/mboot/map.c index 2e8641f..1992f14 100644 --- a/com32/mboot/map.c +++ b/com32/mboot/map.c @@ -281,7 +281,7 @@ struct multiboot_header *map_image(void *ptr, size_t

Hi, I'm trying to get to the bottom of a problem using the combination of tboot (http://tboot.sf.net, trusted boot kernel for Intel TXT) and extlinux. TBOOT loads using the multiboot protocol, where the tboot "kernel" is loaded as the kernel, and the actual linux kernel and initrd are specified as modules. A working grub configuration looks something like:

On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: > On Sun, Jan 4, 2015 at 9:27 AM, gene.cumm at yahoo.com <gene.cumm at yahoo.com> wrote: > > Test from Yahoo via Android > > > > --Gene > > _______________________________________________ > > Syslinux mailing list > > Submissions to Syslinux at zytor.com > > Unsubscribe or set options at:

Intel has VBIOS updates available that end-users typically cannot use unless their vendor includes it in a system BIOS update. The only exception is being able to use a DOS TSR (terminate and stay resident) executable, which doesn?t work e.g. in NT-based Windows. However, I do not know if this also applies to Linux (and that may be a question to ask elsewhere). However, regarding MEMDISK, would it

> On Saturday, January 17, 2015 1:48 AM, Geert Stappers <stappers at stappers.nl> wrote: > > > On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: >?????????? <snip/> > > > As far as I can tell, GMail does process the SPF/DKIM/DMARC properties > > > but ignores

On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: <snip/> > > As far as I can tell, GMail does process the SPF/DKIM/DMARC properties > > but ignores Yahoo!'s DMARC policy to reject on failure. > > The Syslinux ML should now be ready for DMARC p=reject > > We shall see how

On Thu, Sep 24, 2015 at 07:57:47AM -0600, Alan Sparks via Syslinux wrote: > On 9/24/2015 4:59 AM, Gene Cumm wrote: > > On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > >> Now I have something I can reproduce. Booting my same ipxe.iso to > >> perform an initial TFTP load shows what I saw already. Attempting to > >>

Hi, It is not important how long I have been moderator for this mailinglist. Thing is that I'm thinking about stepping back. How would like to help the Syslinux project by moderating this ML? Groeten Geert Stappers -- Leven en laten leven ------------- volgend deel ------------ Een niet-tekst bijlage is gescrubt... Naam: signature.asc Type: application/pgp-signature Grootte: 836 bytes

Hello, A `make efi32` yeilds me make[3]: *** No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `efi32/efi' make[2]: *** [efi] Error 2 Output of `ls -Gl efi32/com32/lib/mem*.o`: -rw-r--r-- 1 stappers 2812 Jun 10 22:06 efi32/com32/lib/memcpy.o -rw-r--r-- 1 stappers 3620 Jun 10 22:06 efi32/com32/lib/memmem.o

Hi, Since which version of pxelinux.0 is understood in pxelinux.cfg/default that kernel http://host.lan/netboot/vmlinuz means vmlinuz should be transported over HTTP? Since which version of pxelinux.0 is it possible to boot on UEFI? Those questions elaborated: What I want is fast netboot UEFI servers. What I'm looking for is an advice which version of PXELINUX between version

Hello, I am trying to flash new firmware into a router using TFTP-HPA. I am running Ubuntu 14.04 on a flash drive and still learning how to use Linux. I have also installed XINETD.D In one of the README files that comes with TFTP-HPA it said not to call it using tptp. Here are the instructions I'm trying to follow: cd /tmp ; tftp -gl aa 192.168.0.9; sh aa I do not know what

Op 2013-07-13 om 19:58 schreef Michael Szerencsits: > Hi, > > I tested the following config: > > DEFAULT AutoInstall > PROMPT 0 > LABEL AutoInstall > KERNEL http://server/vmlinuz64 > APPEND initrd=http://server/initrd64.img > root=live:http://server/LiveOS/squashfs.img quiet lang=en > keymap=de-latin1 systemd.unit=rescue.target > system.unit=rescue.target

Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > On 06/06/2013 02:40 PM, upen wrote: > > > > Some odd things I observed just now. > > 1. Since yesterday, I have been reseting the client box from Virtualbox VM > > menu (Reset option). This always showed me com32 vesamenu.c32 > > message. > > 2. Some time ago, I decided I power off the client VM(

Op 2014-07-23 om 17:57 schreef Gene Cumm: > On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > > Hi, > > > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > > > kernel http://host.lan/netboot/vmlinuz > > > > means vmlinuz should be transported over HTTP? > > For non-EFI

This patch is just a (shameless) copy from bug #28 [1]. The original patch has been sitting there for a couple of years now, and it was based on Syslinux v 4.05. The patch I am posting here is just a re-base on v.6.03. Whichever inadequate formatting (tabs, trailing spaces...), or any kind of correction that was required for the original patch to be accepted, is probably still required now.

>>> BTW, some time ago I reworked the disk handling API to also support UEFI and then linking it against gnu-efi library. Patrick, I don't know what exactly you did, but follow what I did: http://git.zytor.com/users/pcacjr/syslinux.git/commit/?h=com32-disk-uefi&id=a29ec41c953cea84261b820cd469b090453125f4 Paulo <<< Patch "I" allows core to "run" the

On Fri, Mar 03, 2017 at 07:49:46PM -0500, Gene Cumm wrote: > On Tue, Feb 28, 2017 at 4:19 PM, Geert Stappers wrote: > > > > It is not important how long I have been moderator for this mailinglist. > > Thing is that I'm thinking about stepping back. > > > } Who would like to help the Syslinux project by moderating this ML? > > I'm willing to help with