From: rtos <rtos@rogers.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS]- fat file system (dosfs)
Date: Mon, 04 Jun 2007 06:22:00 -0000 [thread overview]
Message-ID: <1180938116.27331.3.camel@localhost> (raw)
In-Reply-To: <FE7FB54DCB7C6949A1D3F9FF22DA6C135DF8FE@lvl7in-mail01.lvl7.com>
http://elm-chan.org/fsw/ff/00index_e.html
http://elm-chan.org/fsw/ff/en/mkfs.html
> Hi,
> Dosfs code present in CVS is capable of reading and writing to the
> existing dosfs partition.
> It would be nice to have the capability to create a dosfs partition too.
> Any file system expert out here, who can let me know what it takes to
> implement this functionality (license permitted), and if there is free
> source code available somewhere for reference! I'm on search from my
> side.
>
>
> regards,
> Alok
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-06-04 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 17:38 Alok Singh
2007-06-03 20:54 ` Andrew Lunn
2007-06-04 6:22 ` rtos [this message]
2007-06-03 17:43 Alok Singh
2007-06-03 20:41 ` Sergei Gavrikov
2007-06-04 0:44 ` Alok Singh
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=1180938116.27331.3.camel@localhost \
--to=rtos@rogers.com \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).