similar to: syslinux and partition support

> 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 Tue, Jul 15, 2014 at 8:12 PM, Jongi <jongitech at gmail.com> wrote: > Subject: syslinux and partition support I presume this to mean loading files from another file system/partition that's not the current one. Currently, there's a patch set (MultiFS) however it has not been merged at this time. I'd hope for a pre-release including this patch shortly after the full 6.03

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

> 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

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" > >

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

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

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

> -----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

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

From: Raphael S. Carvalho <raphael.scarv at gmail.com> MULTIFS SYNTAX: (hd[disk number]:[partition number])/path/to/file The meaning of this_fs was changed to improve the flexibility of the support. Now, this_fs means the file system being currently used. root_fs was created to save the context of the main file system (where ldlinux.sys lives in). get_fs_info is a function pointer that

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

> 2017. aug. 30. d?tummal, 12:02 id?pontban Aki Tuomi <aki.tuomi at dovecot.fi> ?rta: > > Something goes wrong when opening "Junk" mailbox. Are you sure it exists? Can you doveadm with > > doveadm -Dv search -u email at example.com mailbox Junk savedbefore 30d There is public namespace defined. Maybe that is the problem? doveadm(root): Debug: Loading modules from

> > Can you do > > p *box $1 = {name = 0x5555557e1f18 "Junk", vname = 0x5555557e1f10 "Junk", storage = 0x5555557e1860, list = 0x5555557e1050, v = { is_readonly = 0x7ffff76e5a50 <fail_mailbox_is_readonly>, enable = 0x7ffff76e5a60 <fail_mailbox_enable>, exists = 0x7ffff76e5a70 <fail_mailbox_exists>, open = 0x7ffff76e5e60

I have successfully set up a system with Ices0.4 and IceCast2.20 (and Tunez). It plays well using mpg123 or WinAmp. But I would like to use also my KiSS DVD player for the stream, and I have not been able to do so - It appearently needs 110% SHOUTcast compatibility. So I tried the IceCast2.3.1 - but it still didn't like the KiSS (or the other way around). In stead, I have added a SHOUTcast

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. http://www.syslinux.org/wiki/index.php?title=MEMDISK#-_Passing_ISO_parameter_to_the_kernel 1. bootfrom 2. findiso 3.