similar to: syslinux: possibly unsafe permissions for /tmp

Richard W.M. Jones via Syslinux wrote: > I'm trying to add boot support to > https://github.com/libguestfs/nbdkit/tree/master/plugins/floppy > > This NBD server plugin generates a completely virtual FAT filesystem > and partition table. Nothing is ever written to a file, and it must > run without anything needing to be root, loop mounting etc. Running > "syslinux

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have problems booting linux 2.4.21 with syslinux 2.04 from floppy. Booting with this combination I get the following error: Loading kernel................ Boot failed: please change disks and press a key to continue. (Note: there are exactly 16 dots ".", it this is relevant) The floppy was DOS formatted with mformat and contains

_ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no config.sys, no autoexec.bat, no TSR's, no memory managers. _ The booting floppy includes syslinux.com 6.02. _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted partition each. Executing syslinux.com -i c: (or "d:") results in the following error: "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083

Thanks for responses. I use GRUB as my bootloader in my hard disk now. I have a Windows in sda1, Ubuntu in sda3. If I want to install extlinux to boot Ubuntu, should I follow the steps below? 1. in Ubuntu, go to extlinux folder, run command ./extlinux --install /boot 2. create an extlinux.conf in/boot 3. cd ../mbr 4. cat mbr.bin > /dev/sda (or use dd if=mbr.bin of=/dev/sda bs=404 count=1)

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

If a syslinux floppy does not contain a config file (syslinux.cfg) modules are not being found unless specified with a directory prefix (e.g. /pcitest.c32). The reason is that CurrentDir is only set if there is a config file present. This is a possible regression since commit 68eefb79e2cbb590ebf958dd0c50ce00b941abd2. Before this change RootDir was used in searchdir and now it's CurrentDir

>From the current pathbased branch, linux/syslinux.c, line 421, open() yields an error on a FAT floppy image, 2.88M standard size. At first, this was a floppy that did have a previous version of SYSLINUX installed. I saved that floppy image and tried deleting ldlinux.sys with the same results. I'm still trying to drill away and find more about its status and understand what is

> If a syslinux floppy does not contain a config file (syslinux.cfg) modules are > not being found unless specified with a directory prefix (e.g. /pcitest.c32). > The reason is that CurrentDir is only set if there is a config file present. This is a > possible regression since commit 68eefb79e2cbb590ebf958dd0c50ce00b941abd2. > Before this change RootDir was used in searchdir and now

Hi. I'm trying to make a simple boot floppy that would choose between booting with serial console or with keyboard/screen based on user's input. In the ideal world, I would like to have the following behaviour: On the serial console, it would show the welcome screen and say "Press Enter now to boot from serial console" and on the VGA screen (at the same time) it would

I am trying to use syslinux on a floppy image to create a bootable CD. When I boot (on a number of computers) I only get "Boot error", using the image file on a floppy works. I realize the correct way to do this is using isolinux with no emulation but but I need to do this with syslinux :( I've looked into it and older versions of syslinux dont have this problem. From my research

I'm trying to add boot support to https://github.com/libguestfs/nbdkit/tree/master/plugins/floppy This NBD server plugin generates a completely virtual FAT filesystem and partition table. Nothing is ever written to a file, and it must run without anything needing to be root, loop mounting etc. Running "syslinux --install <something>" is a non-starter. So I've looked at

On 7/30/2013 7:41 PM, Chandler Carruth wrote: > I've not been following this thread at all. However, skimming the original > post, I fail to find a nice summary of what problem is trying to be solved. The proposal is trying to garbage collect symbols that are not referenced during the link step. In addition this proposal can be extended to keep frequently called functions/data closer

Before I reply on-topic, I'd like to request from people participating in this public mailing list to _avoid_ top-posting whenever possible, and when replying, please quote what's relevant only. Now, back to the topic. > " > Booting... > Error loading operating system_ > " > at the bottom of screen and hangs. I can only reboot using ctrl-alt-del. AFAIR,

Correct typos. Improve format for asciidoc-to-manpage conversion. Wrap text. Correct info. Help phase-out deprecated and/or conflicting options. diff U3 /syslinux-6.03/txt/syslinux.txt /wip/txt/syslinux.txt --- /syslinux-6.03/txt/syslinux.txt Mon Oct 06 16:27:44 2014 +++ /wip/txt/syslinux.txt Sat Dec 27 18:20:27 2014 @@ -30,9 +30,10 @@ unmounted file system. For the DOS/Win32/Win64 installers,

Hardware with issue is a Lenovo T410 (circa 2007?): SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is working for Ghostcast/peer to peer. SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is NOT working for Ghostcast/peer to

My ?default? was just a sample to prevent further tl;dr :) Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or X? Which version? Thanks, David Sent from my iPhone > On Feb 1, 2018, at 6:53 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > >> Hardware

I have been using the LEAF Bering firewall for a year or so. It boots with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it formats the diskette as 1680KB. Recently I found a small Compaq 2266 box to replace a larger Compaq 7170 to run the firewall. But when I try to boot the Bering diskette on the 2266 I get the following message: Loading Linux ............ Boot failed:

> Hello, > > I wanted to ask if there's a reason efi/wrapper.{h,c} use __uint*_t > instead of including stdint.h and using the therein defined uint*_t > types? This breaks compilation of the efi blobs on systems with the musl > libc since that doesn't define __uint*_t types. > > -- > Simon Thelen FWIW... As a simple quick basic test, I took the efi32

> Hardware with issue is a Lenovo T410 (circa 2007?): > > SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select > Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is > working for Ghostcast/peer to peer. > > SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select > Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking

On Tue, Jul 30, 2013 at 8:17 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > On 7/30/2013 7:41 PM, Chandler Carruth wrote: > >> I've not been following this thread at all. However, skimming the original >> post, I fail to find a nice summary of what problem is trying to be >> solved. >> > The proposal is trying to garbage collect symbols that