similar to: Please release 6.03

On 04/23/2014 09:06 PM, Ady wrote: > Suggestions and patches are surely welcome. Ady, Mine is only suggestion, and for sure I will just follow what Syslinux developers decide. Thanks. Steven. -- Steven Shiau <steven _at_ stevenshiau org> Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C

I have an issue to boot iPXE with Syslinux 5.01. However, the same method works for Syslinux 4.06. The error messages I got is (see attached png file): =================================== iPXE 1.0.0+git-20120202.f8840ba-3 -- Open Source Network Boot Firmware -- http://ipxe.org Features: VLAN HTTP iSCSI DNS TFTP AoE SRP BzImage COMBOOT ELF MBOOT PXE PXEXT /syslinux/ipxe.lkn: command not found

On Thu, Sep 12, 2013 at 12:24 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 2013/9/12 11:55, Steven Shiau wrote: >> >> Deal developers, >> I'd like to follow the thread >> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html >> but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and >> provide more test cases.

Dear all, I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem is, I have problem to use it for PXE booting (BIOS mode). It always gives me "Failed to load COM32 file vesamenu.c32". I am sure all the settings are correct because if I switch to the prebuilt syslinux downloaded from

On 09/26/2013 01:44 AM, Jeffrey Hutzelman wrote: > Yes; you can configure your DHCP server to hand out different values for > the pxelinux.configfile option to specific clients, matching on MAC > address or a variety of other conditions. Of course, this means that > the config file for that machine will need to know what firmware to > expect and thus what path to set. Hi Jeffrey,

Deal developers, I'd like to follow the thread http://www.zytor.com/pipermail/syslinux/2013-April/019761.html but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and provide more test cases. The pxelinux before version 5, e.g. version 4.06, worked very well with memtest86+ 4.20, all my PXE client machines, including VMWare workstation 9, VirtualBox 4.2, and all the real

On 2014?03?08? 20:57, Gene Cumm wrote: > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > >> > Another thing you I'd like to mentioned is, after bootx64.efi was >> > downloaded, the next download for ldlinux.e64 was about 15 secs later. >> > Is that normal? > When it's successful for me, it takes 0.2s from the beginning of >

/sudo/pseudo code/ On Wednesday, April 23, 2014 9:32 AM, Don Cupp <doncuppjr at yahoo.com> wrote: I actually propose another strategy that may kills many birds with one stone. I think it should be able to be handled internally. Right now, we take a kernel argument as a literal file name hdt.c32 really mean load file hdt.c32. That great, it works, that is how most config files are written.

After switching to version 6.2, I am having a problem to use chain.c32 to boot a local disk. My settings: ====================== label local MENU LABEL Local operating system in hard drive kernel chain.c32 append hd0 ====================== It gave me "Error: Couldn't read the first disk sector" If I change the settings as ====================== label local MENU LABEL

That doesn't seem like a good reason to keep the old code base alive... we need to reduce our support load. Steven Shiau <steven at nchc.org.tw> wrote: > >On 09/27/2013 02:37 AM, H. Peter Anvin wrote: >> "Big jump" in what way? >Oh, I should not use that strong words... Actually what I meant is the >implementation of EFI support so the file directories in the

On Thu, Sep 19, 2013 at 11:59 PM, Steven Shiau <steven at nchc.org.tw> wrote: > > On 09/13/2013 06:36 AM, Gene Cumm wrote: >> I believe this is a result of how/where memtest wants to be loaded. I >> can confirm it's present in 5.11-pre9 but appears resolved for me in >> 6.02-pre16. I should be able to test in Workstation-9.0.2 tomorrow. > Hi Gene, > Were

On 09/25/2013 11:39 PM, Steven Shiau wrote: > > > On 09/24/2013 04:58 AM, Gene Cumm wrote: >> I'm not sure if there will be another 5.xx release or pre-release, >> except possibly more testing with some changes I've made recently for >> lwIP-enabled PXELINUX (lpxelinux.0) > Gene, > Got it. If possible, please have another 5.xx release since 6.x is a big

On 09/26/2013 02:02 PM, Jeffrey Hutzelman wrote: > > Right; you've asked for a feature that doesn't exist. I've given you an > alternative approach you can use with your existing DHCP server that > does not require any new features in Syslinux > It wouldn't be too hard to implement, just a matter of someone finding the time. -hpa

On Wed, Apr 23, 2014 at 7:49 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 04/23/2014 06:12 PM, Gene Cumm wrote: >> Currently, the linker drops text strings into hdt.c32 specifying its >> dependencies and the Syslinux core hunts for those. It would be a change of >> the Makefiles and the list of filename suffixes to attempt which is already >>

On 10/16/2013 06:23 PM, Steven Shiau wrote: > > > On 2013/9/27 ?? 07:28, H. Peter Anvin wrote: >> It wouldn't be too hard to implement, just a matter of someone finding >> the time. >> >> -hpa > > Great! I believe this feature is very useful for a PXE server. > Since syslinux 6.02 is released, may we expect this feature to be added > in 6.03?

Hi folks, While trying to package this release for mageia4, I found that the efi scripts are considering that we do have a git repo while we are supposed to use tarballs. To avoid this issue, I've been adding a very stupid fix to my build. What's you opinion on it ? At least, with it, I can build syslinux from the tarball. Erwan, -------------- next part -------------- A non-text

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

On Apr 23, 2014 5:31 AM, "Ady" <ady-sf at hotmail.com> wrote: > Currently, a Syslinux module that requires another Syslinux Library > module to work looks for its (full) name. For instance, hdt.c32 looks > for several lib*.c32 modules so to be able to work. The searched-for > paths start at the Current Working Directory, and then potentially > continues according to

On 29 October 2013 11:39, Steven Shiau <steven at nchc.org.tw> wrote: > My bad, I meant version 6.02, not 6.2 > > Steven. > > On 10/29/2013 11:28 AM, Steven Shiau wrote: > > After switching to version 6.2, I am having a problem to use chain.c32 > > to boot a local disk. > > My settings: > > ====================== > > label local > > MENU

On 2014/4/23 ?? 09:55, Gene Cumm wrote: > The resulting config would require suffix-less module references, i.e. > "UI menu" or "COM32 ls". > > Additionally, I documented the basics of my test system here: > > http://www.syslinux.org/archives/2014-February/021740.html > > Bear in mind, by "URL-like file locations", I mean that if we have >