similar to: Availability of a variable of the TFTP server IPaddressto be used in pxelinux.cfg/default

Hello Shao, Thank you for your hint. I saw this one already earlier but I wanted to avoid it for two reasons: - One of my images uses a CPIO INITRD which I found rather complicated editing (like I wrote I'm quite new to all that Linux stuff). - For each new release I will need to do the changes to the prebuilt images again. I'm not the one who creates the images. I'm downloading

Hello, I'm new to Linux and quite inexperienced - sorry. I set up about 20 PXE servers with several tools as different boot images. Two of the tools require files to be loaded from the TFTP after the kernel has loaded. Currently I do the following in pxelinux.cfg/default: label abc kernel def append TFTP://2.3.4.5/xyz My PXE boot images are set on one master server and from there

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

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

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]

> -----Original Message----- > From: Celelibi [mailto:celelibi at gmail.com] > Sent: Wednesday, January 13, 2016 2:22 AM > To: Tal Lubko > Cc: Shao Miller; For discussion of Syslinux and tftp-hpa > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > 2016-01-12 22:21 UTC+01:00, Tal Lubko via Syslinux > <syslinux at zytor.com>:

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:

2016-01-12 22:21 UTC+01:00, Tal Lubko via Syslinux <syslinux at zytor.com>: > On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller via Syslinux wrote: >> 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

On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller via Syslinux wrote: > 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 >

Three commits at my "for_hpa" branch (not derived from any old for_hpa branch you might have). Briefs are below. I'm still working on the DOS installer. - Shao ----- Author: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat Jul 3 16:23:44 2010 -0400 win32: Use libinstaller option parser We will produce an error message if a user attempts to use an option

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

Hi all, First time here, so please be gentle! :) I'm trying to configure a system that will pxeboot and retrieve a kickstart file from a server based on that host's macaddress as part of my Edison project[0] however I'm having issues getting the dns lookup to work and I'm hoping you can help! My pxelinux.cfg/default file is as follows: ======================= default linux

Applies to Syslinux 4.06. Attached, below, and available at: Repository: git://git.zytor.com/users/sha0/syslinux.git Branch: nictype - Shao Miller ----- From 2764e260e12d9769e3b699e4213b9a164e64924a Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Thu, 22 Nov 2012 20:43:25 -0500 Subject: [PATCH] nictype.c32: PXELINUX module to display UNDI NIC bus

Two commits available at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/chain_freeldr --- Author: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sun May 1 13:49:43 2011 -0400 chain: Support loading ReactOS' FreeLdr Use something like: LABEL freeldr COM32 chain.c32 APPEND freeldr=freeldr.sys Signed-off-by: Shao

From 43e0635d7d90f65055d1f49d998974041315f4fc Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Fri, 11 Dec 2009 01:26:59 +0000 Subject: [PATCH] memdisk: Fix "might be used uninitialized" warnings The checksum_buf function was providing an incorrect checksum on at least one build. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca>

Good day to all, For anyone who feels adventurous, there is an experimental memdisk.c32 COMBOOT32 module[1] now outside of the official Syslinux development efforts, which appears to be functional for a few test cases, but should be considered UNSTABLE. It is a work-in-progress, so please do not report bugs for it at this time. It's for use with Syslinux 3.85, specifically. It was too

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

I have been using PXELINUX with the "ipappend 2" option for a long time. To make things a little more user friendly, I decided to set up menus (text menus with menu.c32), but they wouldn't work (blank screen and corrupted menu flashes by when you hit a key). I went through all kinds of combinations of options, and finally found that commenting out the "ipappend 2" line

Hello, I have not been able to get the IPAPPEND option to successfully set the ip parameters for a pxelinux install. I have LABEL install KERNEL pxelinux.cfg/tftpboot.img APPEND initrd=pxelinux.cfg/initrdfs.gz root=/dev/ram IPAPPEND 1 where tftpboot.img is either of http://ftp.debian.org/debian/dists/woody/main/disks-i386/current/ idepci/tftpboot.img

I've just gotten pxelinux working (very cool) to boot a Dell PowerEdge. Everything is great, except for one bit. I turned on the IPAPPEND option, and when the machine boots (configured for nfs-root, IP kernel-level autoconf with no options) it says: "ip-config: incomplete network configuration information". According to the syslinux.doc file, the ipappend option appends a line to