similar to: [RFC/PATCH 2/3] core: MultiFS infrastructure added.

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

From: Raphael S. Carvalho <raphael.scarv at gmail.com> This patch finishes the MultiFS support. init_multifs gets called in the main (startup) function of ldlinux.c32, so MultiFS will be initialized automatically. init_multifs calls enable_multifs (lives in the core) to hook get_fs_info. Subsequent accesses will callback the get_fs_info living in ldlinux.c32. Signed-off-by: Raphael S.

Filesystem UUID shows the partition we boot kernel from. The kernel parameter has format like FSUUID=DA1A-0B2E. The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. The patch is based on 67aaaeeb228. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- com32/include/syslinux/sysappend.h | 1 + core/fs/btrfs/btrfs.c | 3 ++- core/fs/ext2/ext2.c

Check if fs_ops->readdir is available before calling it. At least PXELINUX doesn't implement it. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/core/fs/readdir.c b/core/fs/readdir.c index d2b112b..d20fc33 100644 --- a/core/fs/readdir.c +++ b/core/fs/readdir.c @@ -28,8 +28,11 @@ struct dirent *readdir(DIR *dir) struct file *dd_dir = (struct file *)dir;

Hi hpa, I just added the generic path_lookup function for EXTLINUX. hpa, It changed a lot, so I want hear something from you. First , here is the main skeleton of the generic path_lookup function: > if (*name == '/') { > inode = this_fs->fs_ops->iget_root(); // The way to get the root > inode is different from different fs > while(*name == '/') >

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Most of file system drivers initialize the cache themselves. The problem is that the same cache could be again initialized later, then invalidating the previous one. This patch fixes this. Problem found while auditing the code. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> --- core/fs/cache.c | 2 ++

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

Ady, Peter, et al. On Fri, July 24, 2015 5:28 pm, Ady via Syslinux 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.

On 05/10/2013 06:27 AM, syslinux-bot for Matt Fleming wrote: > > diff --git a/efi/main.c b/efi/main.c > index 31f0bff..27e7f8f 100644 > --- a/efi/main.c > +++ b/efi/main.c > @@ -1177,13 +1177,10 @@ static void efi_setcwd(CHAR16 *dp) > > EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) > { > + EFI_PXE_BASE_CODE *pxe; > EFI_LOADED_IMAGE *info;

> If I understand the syntax correct, it is: > (hdX,Y)/path/to/file", where X is disk number and Y is partition number. > As far as I understand X and Y are zero based. > > I've tested it with qemu and 2 disks: > - the first with bootloader > - the second with kernel+rootfs > > I've used the following configuration file label: > > label MULTIFS >

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.0-5 Severity: important The hypervisor loads OK but then fails to load my dom0 kernel. I get an erorr message "not an ELF binary" followed after 5s by a hypervisor reboot. /boot/grub/grub.cfg contains: menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux 2.6.22-3-vserver-amd64 (single-user mode)" { set root=(hd0,1)

... 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" http://git.zytor.com/users/pcacjr/syslinux.git/tree/core/include/multifs.h?h=multifs-for-upstream#n27 * MULTIFS SYNTAX: * (hd[disk

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

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

> 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

MultiFS is a new feature that will turn the task of using multiple disks/partitions possible. By the way, it's not mainstream yet. It will only be available when the patches be released or get merged into the official tree. I'm currently working on the last details, thus it isn't yet available to the public. It was previously called Multidisk. But MultiFS seems to cover better both

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

On Wed, Jun 4, 2014 at 6:17 PM, H. Peter Anvin <hpa at zytor.com> wrote: > It would be good to clean it up so out can be used for both. Just teach it that ) ends the parse. Sounds reasonable, I will do that! > > 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

> 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 should be allowed too (please read the whole email thread): http://www.syslinux.org/archives/2014-June/022173.html Examples: __ Space