search for: generic_mangle_nam

...g.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 character. I think that means that later, we'll end up padding with the incorrect n...

...;Current Working Directory" is supposed to be the first searched-for directory, always; the specific location of the main c32 file does not modify the priority of the searched-for list of its dependencies. (snip) > > 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 character. I think that means that later, we'll end up > padding...

...,7 +348,7 @@ const struct fs_ops ext2_fs_ops = { .fs_flags = FS_THISIND | FS_USEMEM, .fs_init = ext2_fs_init, .searchdir = NULL, - .getfssec = generic_getfssec, + .getfssec = ext2_getfssec, .close_file = generic_close_file, .mangle_name = generic_mangle_name, .load_config = generic_load_config, diff --git a/core/fs/ext2/ext2_fs.h b/core/fs/ext2/ext2_fs.h index 8adc9bb..62cbc4a 100644 --- a/core/fs/ext2/ext2_fs.h +++ b/core/fs/ext2/ext2_fs.h @@ -31,10 +31,12 @@ #define EXT2_TIND_BLOCK (EXT2_DIND_BLOCK+1) #define EXT2_N_BLOCKS (EXT2_TIND_BLOC...

...+} + +const struct fs_ops ufs_fs_ops = { + .fs_name = "ufs", + .fs_flags = FS_USEMEM | FS_THISIND, + .fs_init = ufs_fs_init, + .searchdir = NULL, + .getfssec = generic_getfssec, + .close_file = generic_close_file, + .mangle_name = generic_mangle_name, + .open_config = generic_open_config, + .readlink = NULL, + .readdir = ufs_readdir, + .iget_root = ufs_iget_root, + .iget = ufs_iget, + .next_extent = ufs_next_extent, +}; diff --git a/core/fs/ufs/ufs.h b/core/fs/ufs/ufs.h new file mode 100644 ind...

...+} + +const struct fs_ops ufs_fs_ops = { + .fs_name = "ufs", + .fs_flags = FS_USEMEM | FS_THISIND, + .fs_init = ufs_fs_init, + .searchdir = NULL, + .getfssec = generic_getfssec, + .close_file = generic_close_file, + .mangle_name = generic_mangle_name, + .open_config = generic_open_config, + .readlink = NULL, + .readdir = ufs_readdir, + .iget_root = ufs_iget_root, + .iget = ufs_iget, + .next_extent = ufs_next_extent, +}; diff --git a/core/fs/ufs/ufs.h b/core/fs/ufs/ufs.h new file mode 100644 ind...

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Wrote the documentation below. I think it would be good to push the doc to the wiki as soon as the UFS support gets merged. Unix Fast File System (UFS/FFS) 1/2 on Syslinux - (usage/install) ----- There is a confusion about the name of this file system, then I decided to contact the author who replied: "The name has always been

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Change since v1: * Fix bug on dentry structure (thank you specification; btw, sarcasm), and consequently a bug on ufs_readdir. * Add readlink support (applied tests for symlinks whose destionation path were stored in blk pointers and the file itself). * Several improvements. Wrote the documentation below. I think it would be good to

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

....fs_name = "xfs", + .fs_flags = FS_USEMEM | FS_THISIND, + .fs_init = xfs_fs_init, + .iget_root = xfs_iget_root, + .searchdir = NULL, + .getfssec = xfs_getfssec, + .load_config = generic_load_config, + .close_file = generic_close_file, + .mangle_name = generic_mangle_name, + .readdir = xfs_readdir, + .iget = xfs_iget, + .next_extent = xfs_next_extent, + .readlink = xfs_readlink, +}; diff --git a/core/fs/xfs/xfs.h b/core/fs/xfs/xfs.h new file mode 100644 index 0000000..da57221 --- /dev/null +++ b/core/fs/xfs/xfs.h @@ -0,0 +1,752 @@ +/* + * Copyright (...

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