From: Jens Langner <Jens.Langner@light-speed.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.11.4 1/1] fs: new filesystem implementation VXEXT1.0
Date: Fri, 18 Mar 2005 10:22:32 +0100 [thread overview]
Message-ID: <423A9DD8.9080900@light-speed.de> (raw)
In-Reply-To: <20050317184601.GA15228@taniwha.stupidest.org>
Chris Wedgwood wrote:
>>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.
>
> Can this not then be folded into the existing vfat filesystem?
Sure it can. But I thought that as the VXEXT1.0 filesystem is per
definition not a vfat filesystem it might be better to have it separated
and not drill it into the IMHO anyway overly mixed up vfat/fat code
already in the linux kernel tree. Even if that means that some parts in
the code of the vxext filesystem are probably equal to the msdos
implementation, please note that large parts which were not needed by
the vxext implementation was dropped by me for clarifications.
So I still hope that my implementation is going to be considered for a
future kernel tree integration as it may be quite usefull for embeeded
systems wanting to access VxWorks partitions.
cheers,
jens
--
Jens Langner Ph: +49-351-4716545
Lannerstrasse 1
01219 Dresden Jens.Langner@light-speed.de
Germany http://www.jens-langner.de/
prev parent reply other threads:[~2005-03-18 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 15:16 [PATCH 2.6.11.4 1/1] fs: new filesystem implementation VXEXT1.0 Jens Langner
2005-03-17 18:20 ` Sam Ravnborg
2005-03-17 18:24 ` Jens Langner
2005-03-17 18:46 ` Chris Wedgwood
2005-03-18 9:22 ` Jens Langner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=423A9DD8.9080900@light-speed.de \
--to=jens.langner@light-speed.de \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox