public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <w3sg@SoftHome.net>
To: Alok Singh <aloks@broadcom.com>
Cc: eCos discuss list <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS]-  fat file system (dosfs)
Date: Sun, 03 Jun 2007 20:41:00 -0000	[thread overview]
Message-ID: <20070603203930.GA12163@ubuntu> (raw)
In-Reply-To: <FE7FB54DCB7C6949A1D3F9FF22DA6C135DF900@lvl7in-mail01.lvl7.com>

On Sun, Jun 03, 2007 at 11:13:23PM +0530, Alok Singh wrote:
> 
> 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. 

If you didn't mean to create it under eCos..., you can use Linux as well

32 Mb ms-dos disk

1) dd if=/dev/zero of=/tmp/msdos count=64k 	;# 512x64k room
2) mkfs.msdos /tmp/msdos, or mkmsdos /tmp/msdos ;# create ms-dos fs
3) mount /tmp/msdos /mnt/disk -oloop,rw 	;# mount, do it as root

I think that using `mtools', you can mformat it, mcopy files there, etc.

Sergei


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-06-03 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 17:43 Alok Singh
2007-06-03 20:41 ` Sergei Gavrikov [this message]
2007-06-04  0:44   ` Alok Singh
  -- strict thread matches above, loose matches on Subject: below --
2007-06-03 17:38 Alok Singh
2007-06-03 20:54 ` Andrew Lunn
2007-06-04  6:22 ` rtos

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=20070603203930.GA12163@ubuntu \
    --to=w3sg@softhome.net \
    --cc=aloks@broadcom.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).