search for: this_fs

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 will be later hooked to a function from ldlinux.c32....

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 == '/') > name++; > } else { > inode = this_inode; // pwd > } > parent = inode; > > while (...

...> #include <fcntl.h> #include <dprintf.h> +#include <syslinux/sysappend.h> #include "core.h" #include "dev.h" #include "fs.h" @@ -374,6 +375,13 @@ __export void close_file(uint16_t handle) } } +__export char *fs_uuid(void) +{ + if (!this_fs || !this_fs->fs_ops || !this_fs->fs_ops->fs_uuid) + return NULL; + return this_fs->fs_ops->fs_uuid(this_fs); +} + /* * it will do: * initialize the memory management function; @@ -440,4 +448,8 @@ void fs_init(const struct fs_ops **ops, void *priv) SectorShift = fs.s...

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

So in NTFS, the Master File Table is itself a file. That means it can have extents. An easy way to process its records is thus to read it as a file using functions in core/fs/fs.c. However, the functions in core/fs/fs.c mostly assume the "global," Syslinux, booted-from filesystem ('this_fs'). The Syslinux filesystem drivers try to tie all data to a particular FS instance. So if an FS driver wants to open a file, it probably wants to do it _from_ a particular FS instance, such as opening the MFT. Anyway, please see commit bcb5af34d4fd02c5bd2970c89d30275cd9176168[1] and please a...

...che_size); + dev.cache_init = 0; /* Explicitly set cache as uninitialized */ return &dev; } diff --git a/core/fs/fs.c b/core/fs/fs.c index 8c1feea..d6da8a5 100644 --- a/core/fs/fs.c +++ b/core/fs/fs.c @@ -422,8 +422,9 @@ void fs_init(const struct fs_ops **ops, void *priv) } this_fs = &fs; - /* initialize the cache */ - if (fs.fs_dev && fs.fs_dev->cache_data) + /* initialize the cache only if it wasn't already initialized + * by the fs driver */ + if (fs.fs_dev && fs.fs_dev->cache_data && !fs.fs_dev->cache_init)...

...ds to manipulate the current working directory. (see core/fs/lib/searchconfig.c) But that leads into a maze of twisty passages of virtual functions, default implementations and other stuff I haven't figured out yet. Also, what's the difference between CurrentDirName[] and config_cwd[] and this_fs->cwd_name? While trying to figure all that out, I found this in generic_mangle_name() which looks wrong to me. When collapsing repeat slashes (should we also be stripping repeat backslashes here?), we decrement i which is the "space left" count, but we haven't actually copied a c...

On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.

...dlinux.c32"); } diff --git a/core/fs/fs.c b/core/fs/fs.c index 1cb4b00..b6ee19c 100644 --- a/core/fs/fs.c +++ b/core/fs/fs.c @@ -10,8 +10,6 @@ #include "fs.h" #include "cache.h" -__export char *PATH; - /* The currently mounted filesystem */ __export struct fs_info *this_fs = NULL; /* Root filesystem */ diff --git a/core/include/fs.h b/core/include/fs.h index c7d0fd7..b5c7f0d 100644 --- a/core/include/fs.h +++ b/core/include/fs.h @@ -1,6 +1,7 @@ #ifndef FS_H #define FS_H +#include <linux/list.h> #include <stddef.h> #include <stdbool.h> #inc...

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

...dlinux.c32"); } diff --git a/core/fs/fs.c b/core/fs/fs.c index 1cb4b00..b6ee19c 100644 --- a/core/fs/fs.c +++ b/core/fs/fs.c @@ -10,8 +10,6 @@ #include "fs.h" #include "cache.h" -__export char *PATH; - /* The currently mounted filesystem */ __export struct fs_info *this_fs = NULL; /* Root filesystem */ diff --git a/core/include/fs.h b/core/include/fs.h index c7d0fd7..b5c7f0d 100644 --- a/core/include/fs.h +++ b/core/include/fs.h @@ -1,6 +1,7 @@ #ifndef FS_H #define FS_H +#include <linux/list.h> #include <stddef.h> #include <stdbool.h> #inc...

On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > Either that or make the path a list rather than a string, using the > normal word separators when entered on the command line, a bit like the > (t)csh does. That is a bigger change but is probably a better solution. How would this solution handle filenames containing spaces? Would we need to escape (presumably with a backslash)

...e/fs/fs.c > index 1cb4b00..b6ee19c 100644 > --- a/core/fs/fs.c > +++ b/core/fs/fs.c > @@ -10,8 +10,6 @@ > #include "fs.h" > #include "cache.h" > > -__export char *PATH; > - > /* The currently mounted filesystem */ > __export struct fs_info *this_fs = NULL; /* Root filesystem */ > > diff --git a/core/include/fs.h b/core/include/fs.h > index c7d0fd7..b5c7f0d 100644 > --- a/core/include/fs.h > +++ b/core/include/fs.h > @@ -1,6 +1,7 @@ > #ifndef FS_H > #define FS_H > > +#include <linux/list.h> > #inc...

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

...*file, uint32_t type) { uint8_t keeppxe = 0; const union syslinux_derivative_info *sdi; @@ -97,7 +98,7 @@ void chainboot_file(const char *file, enum kernel_type type) * superblock. */ if (sdi->c.filesystem == SYSLINUX_FS_SYSLINUX && - type == KT_BSS && this_fs->fs_ops->copy_super(buf)) + type == IMAGE_TYPE_BSS && this_fs->fs_ops->copy_super(buf)) goto bail; if (sdi->c.filesystem == SYSLINUX_FS_PXELINUX) { diff --git a/com32/elflink/ldlinux/config.h b/com32/elflink/ldlinux/config.h index 4583202..ea4736e 100644 --- a/com32/...

...l; /* DS:SI points to partition info */ @@ -97,7 +97,7 @@ void chainboot_file(const char *file, enum kernel_type type) * superblock. */ if (sdi->c.filesystem == SYSLINUX_FS_SYSLINUX && - type == KT_BSS && vfat_copy_superblock(buf)) + type == KT_BSS && this_fs->fs_ops->copy_super(buf)) goto bail; if (sdi->c.filesystem == SYSLINUX_FS_PXELINUX) { diff --git a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c index 97e5116..f713eb1 100644 --- a/com32/elflink/ldlinux/execute.c +++ b/com32/elflink/ldlinux/execute.c @@ -92,7 +...

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse