similar to: [fsc]Adding a generic path_lookup function in VFS

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

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

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

Currently, I'm looking at implementing 3 COMBOOT API calls for directories, opendir, readdir, and closedir. In order to track progress within the directory, I'll need to keep track of the current sector number that is being read and the offset within the sector for the next file entry to read. I'm contemplating if I should also keep track of the starting sector of the directory (in

This is a possible implementation for syslinux.initramfs_add_file() for the lua.c32 module, it adds a third parameter not documented, the dst_filename as it is required for placing the new file in the initramfs: ########################################################### --- syslinux.orig/com32/lua/src/syslinux.c 2011-03-29 16:52:37.161106252 -0300 +++ syslinux/com32/lua/src/syslinux.c 2011-03-29

Hi, I used scp in some background process for transferring large files which took some hours. For this I needed a less fancy output, preferable parseble by a script, so I could regularly see how far the transfer was The adaptions I made to progressmeter.c and .h are underneath my mail as a patch Some sample output how it looks now: :~/src/openssh-5.3p1$ ./scp -l 60000 test.bin hans at

This is a small patch to progressmeter.c that provides peak throughput information. It adds a new field on the progress bar line that displays the 1sec throughput for the connection. At the end of the transfer it spits out the peak throughput seen. I found it useful in some testing situations and maybe someone else might find it handy. --- ../openssh-4.7p1.logging_features/progressmeter.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;

On Sat, Dec 24, 2005 at 11:03:36PM +0300, Andrey J. Melnikoff (TEMHOTA) wrote: > Hello. Hi Andrey, > Please, CC me, i'm not subscribed. > > Kernel 2.6.15-rc6 OOPS: > > kernel: general protection fault: 0000 [#1] > kernel: SMP > kernel: Modules linked in: ipt_REDIRECT ipt_LOG ipt_TOS ipt_TCPMSS ipt_tos > ip_nat_ftp ipt_tcpmss iptable_nat ip_nat iptable_mangle

Hi, Martijn sent the following patch to me in private and agreed that i post it here. In any other program in OpenBSD base, i'd probably agree with the basic approach. Regarding OpenSSH, however, i worry whether wcwidth(3) can be used. While wcwidth(3) is POSIX, it is not ISO C. Does OpenSSH target platforms that don't provide wcwidth(3)? If so, do you think the problem can be solved

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;

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.

Hi, C/H/S addressing and reading of first block seems to be ok in isohdpfd.bin. The main suspect for the failure of the attempt with isohdpfd.bin is the number or content of the blocks read after the first one. But i have no clue why isohdpfc.bin should do better than isohdpfd.bin. They differ just by one instruction (JC = 0x72 versus JMP = 0xEB) which both are performed before the reading and

In 'core/fs/fs.c', 'fs.root' is set, but the 'iget_root' function pointer call might return a null pointer and we don't check for it. A symptom was that QEmu crashed as EIP landed outside of memory. - Shao /* start out in the root directory */ if (fs.fs_ops->iget_root) { fs.root = fs.fs_ops->iget_root(&fs); /* Maybe we should

I guess this could be filed under the 'shot myself in the foot' section, but I figured I'd report it anyways.. Kernel 2.5.50-bk6, x86, preempt, PIIX IDE, ext3 fs. I dd'ed the first part of a ext3 partition to tmp, then mounted it via loopback. (the image passed a fsck, except for warning about corrupt part. table or superblock) I tried to 'cd' into a directory within

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

Hi, I'm using py-rrdtool 0.2.1 with rrdtool 1.3.0 under 7.0-STABLE, and there's a couple of things about this new version of rrdtool that hurt performance under FreeBSD, but apparently help on whatever they tested on. For every update, the database file is opened, mapped into memory, madvise() is called, contents are modified, msync() is called, and the file is unmapped and closed:

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

The ext2 filesystem supports volume UUID now. The FSUUID variable can be set to kernel command line. Patch is based on FSUUID for FAT patch. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- core/fs/ext2/ext2.c | 40 +++++++++++++++++++++++++++++++++++++++- core/fs/ext2/ext2_fs.h | 1 + 2 files changed, 40 insertions(+), 1 deletion(-) diff --git a/core/fs/ext2/ext2.c

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