similar to: timeout and menu passwd in pxelinux

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.

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu have different background color than that in 3.20. 1. use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu is: http://lfod.nchc.org.tw/stick/syslinux/syslinux_menu_3.30_pre1.jpg 2. use the menu.c32 from SYSLINUX 3.20, the simple menu is:

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

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 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

First I would like to say thank you to HPA for providing some really nice features in recently syslinux version. About new functions, actually I have another radical idea, since we are in Asia, most of the users here they would like to see some local fonts for the syslinux/pxelinux menu. I am wondering is that possible, in the future, the syslinux/pxelinux menu can support CJK fonts or icon ?

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

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 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

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

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

Hi, Sorry for asking this again if this have been asked. I searched this mailing list but I can not find the confirmed answer. We tried to use syslinux to boot USB flash drive. The problem is, if we put the kernel and initrd in /casper directory, syslinux failed to boot, it showed us: ------------------ Booting error message: SYSLINUX 3.11 Debian-2007-03-12 EBIOS boot: /casper/vmlinuz1 Could not

Hi. I need to create a lot of directories, just the same with remote's /var, but I only need the directories, the files inside those sub-directories in /var/ are not necessary for me. I know "find+cp" can do, but I would like to use the archive mode, i.e. I need the original permision, owner, group... Can I make it using rsync ? If so, please tell me how. Thank you in advance. --

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 >

On 03/08/2014 10:06 PM, Gene Cumm wrote: >> Hi Gene, >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got >> > the same issue. My client machine >> > still only shows: >> > ==================== >> > Getting cached packets >> > My IP is 192.168.120.1 >> > ==================== >> > The syslog log

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,

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

On 09/13/2013 06:36 AM, Gene Cumm wrote: > 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

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