Displaying 20 results from an estimated 20000 matches similar to: "SYSLINUX 2.12-pre2 released"
2004 Nov 17
1
SYSLINUX 2.12-pre1 released: initial libcom32 release
Hi all,
I have released SYSLINUX 2.12-pre1. This version has an initial version
of libcom32, a small C library based on klibc for writing com32 programs
in C. It is far from perfect yet, but it should be a lot easier to use
than hand-coding everything.
As usual, find this stuff in:
ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/
-hpa
2004 Nov 29
1
syslinux-2.12-pre1 install bug
Probably have already seen this, but since I didn't see in the email
archives:
thune:/usr/src/syslinux/syslinux-2.12-pre1# make install
make -C sample com32 all
make[1]: Entering directory `/usr/src/syslinux/syslinux-2.12-pre1/sample'
make[1]: *** No rule to make target `com32'. Stop.
make[1]: Leaving directory `/usr/src/syslinux/syslinux-2.12-pre1/sample'
make: *** [installer]
2006 Sep 01
2
SYSLINUX 3.30-pre1 released
Hi all,
I have pushed out a SYSLINUX 3.30-pre1. The main difference versus
earlier versions is that this version contains a *preview* of a VESA
graphical menu system (vesamenu.c32); it's used the same way as
menu.c32, with the addition of a few more commands (which can also be
used in menu.c32 in this new version):
MENU BACKGROUND file.png
... loads a background image in PNG format.
2019 Feb 07
2
syslinux-6.04-pre2
On 2/7/19 4:03 AM, Joakim Tjernlund wrote:
>>>
>>> Hi,
>>>
>>> I merged your tree and added the install patch on top of it. Thank you!
>>>
>>> -hpa
>>
>> Is it worth doing another -pre immediately since upgrading gnu-efi
>> took such a large leap? My thought is if someone has an issue with
>> the new proposed
2019 Feb 07
2
syslinux-6.04-pre2
On Thu, 2019-02-07 at 21:49 +0000, Joakim Tjernlund via Syslinux wrote:
> On Thu, 2019-02-07 at 13:14 -0800, H. Peter Anvin wrote:
> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >
> >
> > On 2/7/19 4:03 AM, Joakim Tjernlund wrote:
> > >
2019 Feb 07
0
syslinux-6.04-pre2
On Thu, 2019-02-07 at 13:14 -0800, H. Peter Anvin wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On 2/7/19 4:03 AM, Joakim Tjernlund wrote:
> > > > Hi,
> > > >
> > > > I merged your tree and added the install patch
2018 Apr 06
2
EFI Clients Unable to Load kernel/initrd Not Stored on PXE Server
Issue Statement:
PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and kernel are on PXE server.
Using packet captures I see that the URI request for the remote file on the repo
2019 Feb 08
0
syslinux-6.04-pre2
On 2/7/19 1:53 PM, Joakim Tjernlund wrote:
\>>>
>>> -z muldefs would bloat the libraries unnecessarily, but worse it might
>>> mask real errors.
>>
>> Looking into the debian patches posted here I see that not using -z muldefs causes
>> bugs. I think you should just use muldefs and report the duplicated memset/memcpy syms
>> in gnu-efi as an bug
2019 Feb 08
2
syslinux-6.04-pre2
On Thu, 2019-02-07 at 20:17 -0800, H. Peter Anvin wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On 2/7/19 1:53 PM, Joakim Tjernlund wrote:
> \>>>
> > > > -z muldefs would bloat the libraries unnecessarily, but worse it might
2004 Dec 03
3
libcom32 license and linking
Peter-
Can you please clarify the license of libcom32, from
the samples directory in syslinux? I am attempting to
create .c32 files that are not encumbered by the GPL,
but the conio.c file states that is is covered by the
GPL. So far, I have resisted linking with libcom32.a,
but is it really your intent to license the library
code under GPL, and not something more like the LGPL?
2009 Nov 27
3
HDT 0.3.6-pre2 is out !
The -pre2 version of HDT 0.3.6 is out.
Gert was a great source of motivation for making that -pre2.
He found many bugs and gave nice ideas.
Thanks Gert for your time and your _many_ tests.
This release will be more or less what will be included in the incoming
syslinux 3.84.
Since -pre1, here come the Changelog
* Reporting CPU L1 & L2 cache
* Report "Hw.Virt" in cpu
2009 Nov 27
3
HDT 0.3.6-pre2 is out !
The -pre2 version of HDT 0.3.6 is out.
Gert was a great source of motivation for making that -pre2.
He found many bugs and gave nice ideas.
Thanks Gert for your time and your _many_ tests.
This release will be more or less what will be included in the incoming
syslinux 3.84.
Since -pre1, here come the Changelog
* Reporting CPU L1 & L2 cache
* Report "Hw.Virt" in cpu
2019 Oct 04
2
syslinux.efi and vendor-class-identifier
Ady Ady via Syslinux wrote:
>
>> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1)
>> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the
>> syslinux-6.04-pre2 distro alongside the existing pxelinux.0
>
>
> Please avoid the official binaries from Syslinux 6.04-pre2 and
> 6.04-pre3. Additionally, the current git
2020 Jul 23
2
extlinux - Failed to load ldlinux.c32
Thank you for your answer. I need to correct some information from my
previous post: booting from `/` did not work either. I just assumed it
did based on previous experience. But with that successful build on
development branch, it did not either.
> I would suggest trying first the official binaries that are already
> included in the official distribution archive (6.03-pre1). Let me
2019 Oct 07
0
syslinux.efi and vendor-class-identifier
On Fri, Oct 4, 2019 at 7:47 AM James Pearson via Syslinux
<syslinux at syslinux.org> wrote:
>
> Ady Ady via Syslinux wrote:
> >
> >> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1)
> >> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the
> >> syslinux-6.04-pre2 distro alongside the existing pxelinux.0
2019 Feb 07
2
syslinux-6.04-pre2
On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux
<syslinux at zytor.com> wrote:
>
> On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote:
> > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote:
> >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote:
> >>> CAUTION: This email originated from outside of the organization. Do
2018 Nov 17
0
fixing debian's hd-media image
> On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
> >
> > Here are some comments and questions for you.
> >
>
> Thanks.
>
> I've have my scripts to a better state, including installing/using
> qemu to uefi and legacy boot the usb stick for testing.
>
> It mostly works for me, but the "wget a tarball of
2012 Nov 09
1
Syslinux-6.00-pre1
I've just pushed out a 6.00-pre1 release. This release includes support
for booting EFI machines. The code is currently in the alpha stage.
Having said that, you should expect most things to work correctly,
including things like the graphical menu.
Please help test if you can, and if you find any bugs, please report
them.
To facilitate building different versions of syslinux.efi (32-bit and
2004 Sep 26
1
[repost] Problem compiling 2.6.3.pre1 and pre2 under Cygwin with Mingw
Can anybody offer usggestions on what to do, or where else to ask?
thanks --nils.
Hello, I'm trying to compile rsync under Cygwin using Mingw, but without
success so far. The same problem appears in pre2.
$ CC='gcc -mno-cygwin' ./configure --build=mingw32
configure: Configuring rsync 2.6.3pre1
checking build system type... i386-pc-mingw32
checking host system type...