similar to: Using MTOOLS in place of loopback mounting

Fellow syslinux fans, I'm using syslinux on a boot floppy (I'll call this syslinux A) to invoke an etherboot image (zlilo style) which invokes a tagged NBI image from my DHCP/TFTP server. The tagged NBI image is created using mknbi-dos and also uses syslinux (I'll call this syslinux B), a linux kernel and an initrd file. It works perfectly if syslinux A has a basic .CFG, e.g.:

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy

From: Gene Cumm <gene.cumm at gmail.com> mtools/syslinux.c: Silence warnings from GCC with asprintf's attribute warn_unused_result in certain glibc versions/patches. Assign it to a variable and ignore it as the string is already tested for null before using it. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- diff --git a/mtools/syslinux.c b/mtools/syslinux.c index

I have just received some audit info on the SYSLINUX 2.01 installer running setuid. There seems to be some issues, and although I can fix them easily enough I'm somewhat questioning the whole approach. The other alternative would be to make the syslinux installer a wrapper around mtools, and use mtools for the filesystem access. Since this would be done entirely in userspace, as a normal

Peter, I'm a new user of Linux trying to use the SYSLINUX boot loader to create a Linux system. I'm doing it on a PC with WIN98 installed, and I prefer using a dual boot system. I got through as far as creating a semi-bootable floppy. The problem I'm getting states "could not find kernel image: Linux." However, I do get the "boot:" prompt as well (I just

hello. I found there are a few mistakes in linux/syslinux.c (hope i'm not wrong since it's my first patch). diff --git a/linux/syslinux.c b/linux/syslinux.c index 37a54fd..5d38e6f 100644 --- a/linux/syslinux.c +++ b/linux/syslinux.c @@ -316,7 +316,6 @@ void do_umount(const char *mntpath, int cookie) int main(int argc, char *argv[]) { static unsigned char sectbuf[SECTOR_SIZE]; -

Seth, Thank you for your reply. I'm sorry to bother with this, but what is the "root pivot" function and where can I find doc's on it. From what I understand from your email the system would basically boot twice. Once from a stripped kernel on the floppy disk to mount the CD, and then after the CD is mounted it would reboot with the kernel and initial randisk found on the

Hi, is there an option to have the DISPLAY command issue a pause after each screen full of information? I've been searching for a way to have users to agree to (or at least be able to read ) the GPL license. "by issueing a command other than F2 you agree that you are bound to the terms of the GNU Public License that is used on this FreeDOS beta9 cdrom. You can read the license terms by

On Thu, Dec 13, 2018 at 10:57 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I'll repeat what I said in my prior email: you don't have to keep > looking, we already achieved what you want (considering that you are > willing to "disregard" the screen problems and similar issues, at least > for now, according to your own emails).

Hi, I'm sorry to bring this up again but I can't quit get this too work. I'm trying to build a 2.88 floppy image so that I can use PXE to load Ghost. I'm useing the following to get a copy of the bootsector: dd if=/dev/fd0 of=bootblock bs=512 count=1 Then I build the image file with: mformat -C -t 160 -s 18 -h 2 -B bootblock x: Then use mcopy to put the required

> > > I think add some lines around here: > > > > > > https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 > > > > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 > > > ::vesamenu.c32; \ > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 > >

I have been having problems with syslinux not working on one system. The error message was "failed to create ldlinux.sys". I checked and mcopy was installed. But upon further investigation I finally found the problem. I were starting syslinux for python (2.4) and in the python code I made it ignore SIGNCHLD. It turns out that this signal state was inherited by syslinux and it made

I tend to use the same tool-chain across various hosts so I made this very simple patch that allows you to pass the cross-compiler name to make ( e.g. make CROSS_COMPILE=i686-nptl-linux-gnu-). I'm not sure if patches should be attached or just pasted inline so I did both this time. BTW, it's relative to syslinux 4 but the same changes work with syslinux 3 although the patch won't

Hi, I've got a couple of questions, I'm trying to get syslinux 2.10 to work on my Apacer Handy Steno TN202 128MB flash drive, I'm getting... root at will # syslinux /dev/sdb1 Total number of sectors not a multiple of sectors per track! Add mtools_skip_check=1 to your .mtoolsrc file to skip this test ...but if I try the same command on a mandrake box the syslinux command is

Hi. I am trying to build a bootable linux CD using isolinux and a cloop image. I am a bit lost right now. What I have done is built a custom distro on a seperate partition on my hard drive. I can boot to it with Grub no problem. I've added the ioslinux directory with isolinux.bin, isolinux.cfg, a kernel (with initrd, loopback, iso support), and an initrd file. My next mission is to some

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

> 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

Having looked at some of the discussions circulating before, I tried the recipe that Bruce Bryne suggested to make a memory stick to be a RedHat EL bootable file system for RedHat installation, but then hit a "missing operating system" problem. Below are the steps I took: a. mkdosfs /dev/sdc1 b. mount /dev/sdc1 /mnt/stick c. cp rhas3u2/isolinux/* /mnt/stick where rhas3u2 is the

On Sat, Nov 17, 2018 at 1:54 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > 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

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 binaries" step isn't going to sit well with