similar to: MultiFS syntax definition

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

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

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

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

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

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 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 have pointed out, I'd rather use a comma, but even more specifically, we already *have* a very sophisticated syntax

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.

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.

From: Raphael S. Carvalho <raphael.scarv at gmail.com> v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems

On Tue, Sep 01, 2015 at 11:40:14PM -0300, Raphael S Carvalho via Syslinux wrote: > On Tue, Sep 1, 2015 at 8:58 PM, Paulo Alcantara via Syslinux < > syslinux at zytor.com> wrote: > > > Hi, > > > > My name is Paulo Alcantara. I've been working on BIOS/UEFI firmware and > > file systems development for a long time already. For those does not > > know,

Check if ldlinux.sys is larger than 64k at build time. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- core/Makefile | 5 +++-- core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 2 deletions(-) create mode 100644 core/ldlinux_limit.pl diff --git a/core/Makefile b/core/Makefile index f795a5c..00de331 100644 ---

From: Raphael S. Carvalho <raphael.scarv at gmail.com> My commit 09f4ac33 broke 'com32/lib/syslinux/disk.c' __lowmem doesn't work for declarations outside the core. Using __lowmem outside the core wouldn't have the desired effect, then lmalloc must be used instead to store dapa into the correct section (".lowmem"). Reported-by: Dark Raven <drdarkraven at

Hi, My name is Paulo Alcantara. I've been working on BIOS/UEFI firmware and file systems development for a long time already. For those does not know, in the past few years I used to be an active Syslinux contributor and added support to NTFS and XFS file systems, GSoC mentor for Syslinux in 2012, did some bugfixes and some code refactoring (e.g. x86 assembly to pure C) and currently working

Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit,

On 07/26/2013 08:10 AM, Matt Fleming wrote: > On Wed, 24 Jul, at 08:05:16AM, Raphael S.Carvalho wrote: >> Check if ldlinux.sys is larger than 64k at build time. >> >> Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> >> --- >> core/Makefile | 5 +++-- >> core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ >> 2