[PATCH 2.6.11.4 1/1] fs: new filesystem implementation VXEXT1.0

From: Jens Langner (Jens.Langner_at_light-speed.de)
Date: 03/17/05

  • Next message: Gene Heskett: "Re: Linux 2.6.11.2"
    Date:	Thu, 17 Mar 2005 16:16:36 +0100
    To: linux-kernel@vger.kernel.org
    
    

    Hi,

    The following URL is link to a large patch for a possible integration of
    a new filesystem implementation in the misc section of the kernel tree.
    It features a reverse engineered implementation of the so called
    VXEXT1.0 DOS filesystem which is commonly used on VxWorks RTOS systems
    from Wind River Inc., where the "extended DOS filesystem" mode is enabled.

    The VXEXT filesystem is more or less a FAT16 based filesystem which was
    slightly modified by Wind River to allow the storage of more than 2GB
    data on a partition, as well as storing filenames with a maximum of 40
    characters length. To achieve that, VxWorks uses a dynamic cluster size
    calculation which is based on the partition size where clusters can be
    larger than 32K. In addition, it uses a slightly modified directroy
    entry structure to allow to store filenames larger than 8+3 characters.

    Please find the patch file accessible through the following URL:
    http://www.jens-langner.de/vxext_fs/vxext_fs_1_0-linux-2.6.11.4.patch

    In addition, refer the detailed technical documentation on my
    implementation and the root directory of my distribution as well:
    http://www.jens-langner.de/vxext_fs/Documentation/vxext.txt
    http://www.jens-langner.de/vxext_fs/

    Please note that large portions of the implementation are based on the
    already existing FAT16 (msdos) implementation in the kernel tree.
    However, instead of patching/drilling the original FAT16 implementation,
    an "outsourced" rework for developing the VEXT implementation was
    considered.

    cheers,
    jens

    -- 
    Jens Langner                                         Ph: +49-351-4716545
    Lannerstrasse 1
    01219 Dresden                                Jens.Langner@light-speed.de
    Germany                                      http://www.jens-langner.de/
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Gene Heskett: "Re: Linux 2.6.11.2"

    Relevant Pages

    • [PATCH 2.6.0-test5 latest bk]mqueue filesystem
      ... changes in 2.6.0-test4 caused your patch to no longer build. ... I have been hammering the hell out of this filesystem ... POSIX message queues fs ... +static int proc_write_max_queues(struct file *file, ...
      (Linux-Kernel)
    • [PATCH 0/4] jbd: possible filesystem corruption fixes (rebased)
      ... Subject: jbd: possible filesystem corruption fixes (rebased) ... This patch set fixes several error handling problems. ...
      (Linux-Kernel)
    • Re: [PATCH] lockfs patch for 2.6
      ... Christoph's vfs patch looks good, I've stripped out the XFS bits (FS ... I had to add a struct super_block pointer to ... * block device, we hould a read lock on the s->s_umount sem to make sure ... Lock the filesystem while a device is suspended. ...
      (Linux-Kernel)
    • Re: [PATCH] Add notification of page becoming writable to VMA ops
      ... >> The attached patch adds a new VMA operation to notify a filesystem or other ... that reduces the size of the patch. ... Linux NTFS maintainer / IRC: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [PATCH] Handle errors in sync_sb_inodes()
      ... time but not reported to the program as shown by the following script ... # We binary search the size of a file in 40M filesystem that can cause ... then expects to find some error code in msync(). ... With this patch, I think it's important to keep the return values of ...
      (Linux-Kernel)