similar to: Boot

Hello, Is it possible for syslinux to boot from a different partition ? I have a UFD with 2 partitions. The first one is fat32 and the second one is a squashfs. I have the OS files in the squashfs partition. As the syslinux won't boot from a squashfs partition, I thought of creating a fat32 (first partition) and install syslinux in it. If I do that, is it possible to configure syslinux to

On 3/3/2016 07:43, Pete Batard via Syslinux wrote: > [...] as far as I am concerned, 'A "version" such as "6.03" [is not] > enough'. [...] I'd like to help to improve Syslinux with regards to version-related concerns. Having typed that, perhaps we could discuss your (or Rufus') specific needs, in parallel? Do I understand correctly that the primary

I'm wondering if it's possible to use isolinux on a bootable CDR to boot an ISO9660 disk image off of the CDR's filesystem. I'm trying to make a multi-boot CD which is capable of booting both floppy images and smaller ISO9660 images (such as the debian netinst or DSL - damnsmall linux), and I am wondering if isolinux is capable of doing this (or something similar to this -

Hi, some time ago I tried to boot an isolinux boot loader from another one to be able to boot e.g. a Knoppix CD with its original boot loader and menus from a "main" isolinux on a multiboot DVD. This works for isolinux <= 3.07 now! However, newer isolinux boot loaders have some problems and the isolinux (e.g. of the Knoppix CD) loaded from the multiboot DVD's main isolinux

Greetings, I wonder whether there are any plans to build udflinux or the likes. I've searched through the mailing list, finding out that should I create a mixed ISO9660/UDF filesystem. Unfortunately, that is not an option if I want to use a significant feature of UDF filesystem, which is writing. Making a mixed ISO9660/UDF, using mkisofs -udf, will (to my best knowledge) not allow me to

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

> Hi, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed

Hello I have a problem with isolinux my root filesystem is a iso9660 cdrom , it wont start the init but it mounts /dev/hdc as root. Cant linux start directly from a the cdrom or is this another problem? I get this: VFS: Mounted root filesystem (iso9660) readonly Freeing unused kernel memory: 2808kb freead Warning: unable to open an intital console Kernel panic: no init found. try parsing

On 11/24/2013 09:56 AM, Ady wrote: >> The very early code that emits this message is *identical* between >> Syslinux 4 and Syslinux 6. The biggest difference is the size of >> isolinux.bin, so it is possible that that might be the source of the >> problem. >> >> -hpa > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > 2KiB

Hi, i began to implement a common lookup function for SUSP and Rock Ridge entries: /* Obtain the payload bytes of all SUSP entries with a given signature. @param fs The data source from which to read CE blocks. @param dir_rec Memory containing the whole ISO 9660 directory record. @param sig Two characters of SUSP signature. E.g. "NM", "ER", ...

Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: "The additional isohybrid feature for UEFI adds a partition to the MBR partition table pointing to the same file in the ISO 9660 filesystem as does the El Torito catalog entry for EFI." According to this (and can be see using fdisk) it's being created a partition-inside-partition just by setting its start and end

Hi everyone. I need a hint. I have a running pxelinux system with a lot of submenues in production usage. Nearly the same structure I have in production usage from USB-sticks (syslinux and memdisk). No I want to have the same structure also bootable form a CD. Unfotunally my main applications are only available as .iso -files. no chance to get them bootable with eg vmlinuz. The iso contains

On Fri, Sep 18, 2015 at 02:01:32PM +0300, Ady via Syslinux wrote: > > > > We have pxechn.c32 working with pxelinux.0 to switch between the two > > system, but pxechn.c32 under Uefi come up with the folowing error > > > @Developers, please consider using 8.3 file names format for c32 files > instead of such a long file name. Example of such a long file name? So

I have a USB disk with syslinux files installed in /boot/syslinux, and the bootloader is installed into MBR or VBR I then extracted a *.iso file which uses syslinux as the bootloader, into root dir of the disk. The iso file contains a rescue OS or an OS installer. Now I got the directory /isolinux with files isolinux.bin and isolinux.cfg in this folder I can now boot into syslinux, but *what to

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each

I need to make a iso image with the filesystem like nero does and i need it for the windows platform not for linux... I need something that does not restrict filenames, it doesn't boder me that are shortnames as long as it let's me access the directory or filename. This is the commandline I use to compile my iso file: %BASEDIR%\isolinux\buildcd\win32\mkisofs -r -log-file log.txt -J -l

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

Hi, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO

Hi, We are planning to have LVM being used over a network of 3 h/w machines(500 GB Disk each) Each hardware machine will have 2-3 domUs. Can we store these domUs as a Logical Volumes stored across Network of these 3 machines? Can one DomU exceed the 500 GB (physical drive size) and store say 1 TB of data across the networked Physical Volumes? Has anyone done this before? Thanks and regards,

Hi all, Has anyone created a Xen cluster to run a hadoop vm cluster? I would be interested in how it performs Thanks Lance -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users