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

[Jens Langner]

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@xxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/