similar to: Booting from various ISO files directly

> So I'm not sure there is a question here that relates to Syslinux, > but if there is it would be great if you could restate it. The boot parameters ?findiso?and ?iso-scan/filename? were mentioned in an article. http://www.syslinux.org/wiki/index.php?title=MEMDISK#-_Passing_ISO_parameter_to_the_kernel So I assumed that there might be more software developers or system administrators

On 11/14/16 02:10, SF Markus Elfring via Syslinux wrote: > Hello, > > Various boot parameters can be considered in alternative GRUB 2 configurations. > https://help.ubuntu.com/community/Grub2/ISOBoot/Examples > > I would like to clarify command line parameters like the following a bit more > for the purpose of booting ISO images better. >

On Jun 24, 2013 3:28 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > Not unless you explicitly force the OS to include a driver. http://www.syslinux.org/wiki/index.php/MEMDISK#-_Drivers_that_detect_the_MEMDISK_mapped_floppy.2Fdisk.2FISO_image > mattias <mj at mjw.se> wrote: > > >ah i meen that > >so i can boot e.g windows xp? > >let's

Searching threads back to 2013-07-01 (date of last message on thread), I've come up with the folloowing: -Needs review for inclusion: 12/26 Init cache once 11/27 efi PE header set 11/21 FSUUID for ext2 filesystem 10/15 Upgrade to Lua 5.2.2, add filesystem module and get_key binding (21) 09/23 com32: hdt: fix memory leak 10/3/12-12/16 4k sector support 10/18 MultiFS from MultiDisk 10/07 Lua

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

> On 07/23/2015 02:09 PM, Raphael S Carvalho via Syslinux wrote: > >> > > My sincere opinion is to apply this patchset as-is, and incrementally > > improve multifs. Lack of alternatives (additional features) *should not* be > > a reason to block this patchset. Again, I really think that this patchset > > should be applied unless a technical reason, e.g. some

On 20.12.2015 09:55, poma wrote: > ... > > Syslinux MultiFS test: > > - QEMU/KVM SeaBIOS: PASSED > - Bare-metal BIOS: FAILED [1] > - OVMF: FAILED [2] > - Bare-metal UEFI: not tested > > > [1] stalled: > Loading (hd3,2)/vmlinuz-4.3.2-200.fc22.x86_64... > > > [2] "failed: No such file or directory" > >

Is there a method by which one could boot an ISO image from a flash drive with syslinux? -- Dimeneira aka Dime

[This email is either empty or too large to be displayed at this time]

On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/04/2014 11:09 AM, Raphael S Carvalho wrote: >> Before proceeding with the MultiFS patchset, let's discuss the MultiFS syntax. >> >> It's currently as follows: >> (hd[disk number]:[partition number])/path/to/file >> >> Any objections? >> > > As others

Hello Everyone Sometime ago there was some discussion about Syslinux multifs support. I've tested it for some time using qemu and it seems to be working. Lately I've started testing it with my real hardware and for some reason it doesn't work. I don't really know how to debug Syslinux (aside from using printf), so what I've succeeded to discover with is that the

On Fri, Jul 24, 2015 at 3:56 PM, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On 07/23/2015 02:09 PM, Raphael S Carvalho via Syslinux wrote: >>> >> My sincere opinion is to apply this patchset as-is, and incrementally >> improve multifs. Lack of alternatives (additional features) *should not* be >> a reason to block this patchset. Again, I really

On Wed, Jul 22, 2015 at 11:15 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > The MultiFS syntax is basically "(hdX,Y)/path/to/file", where X is disk > > number and Y is partition number. > > > > Thank you. > > As a reminder, please note: > > _ There was a syntax discussion about "multifs", so additional syntax > forms

> -----Original Message----- > From: poma [mailto:pomidorabelisima at gmail.com] > Sent: Tuesday, January 19, 2016 1:30 PM > To: Tal Lubko; 'H. Peter Anvin'; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 19.01.2016 09:07, Tal Lubko via Syslinux

Hi , I ve tested the pclinux minime on usb 1Gb and later 8Gb, with fat32 and syslinux boot , works splendid in Ram , and persistant saves on stick.. Now i want to try extlinux-boot with ext2 or 3 on the usb. With ext3 , i get constantly bumped to commandline, where i could type in the vmlinuz and initrd paths , but it cant make the loop-file of minime work..so it gets little panic :* But it wont

Before proceeding with the MultiFS patchset, let's discuss the MultiFS syntax. It's currently as follows: (hd[disk number]:[partition number])/path/to/file Any objections? Regards, Raphael S. Carvalho

Raphael, Except for the : instead of the , this looks like the grub hard disk nomenclature that's been around for a thousand years. Certainly since early GRUB1. Example: (hd0,0)/grub/splash.xpm.gz Why did you chose : instead of grub's , ? I'm guessing (like grub) that disks & partitions are 0-based? (Were the original grub authors European?) Spike #Date: Wed, 4 Jun 2014

It would be good to clean it up so out can be used for both. Just teach it that ) ends the parse. On June 4, 2014 2:06:22 PM PDT, Raphael S Carvalho <raphael.scarv at gmail.com> wrote: >On Wed, Jun 4, 2014 at 5:36 PM, Raphael S Carvalho ><raphael.scarv at gmail.com> wrote: >> On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> On

> No Syslinux variant can load items outside the current file system > space, yet. SYSLINUX can't load anything outside its current block > file system. ISOLINUX can't load anything outside its current ISO > image. PXELINUX can only load network files. Similar rules apply for > Syslinux EFI based on where it was loaded from. There's a patchset > that will be put

I have LVM volumes: /dev/disk1/main /dev/disk1/mainboot /dev/disk1/other /dev/disk1/otherboot I can boot main by using syslinux with syslinux.cfg including: LABEL main MENU LABEL Main LINUX ../vmlinuz-linux APPEND root=UUID={UUID} {kernel parameters} INITRD ../initramfs-linux.img (1) I see a lot of places saying syslinux can't boot a kernel on another partition, and that you have