From: David Woodhouse <dwmw2@infradead.org>
To: Nandakumar NarayanaSwamy <nanda_kn@rediffmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File systems in embedded devices
Date: 08 Feb 2003 19:41:22 +0000 [thread overview]
Message-ID: <1044733282.2943.34.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <20030208142009.17031.qmail@webmail29.rediffmail.com>
On Sat, 2003-02-08 at 14:20, Nandakumar NarayanaSwamy wrote:
> Dear All,
>
> We are developing a embedded device based on linux. Through the
> development phase we used NFS. But now we want to move some
> filesystem which can be created in FLASH/RAM.
Which? Flash or RAM?
> Can anybody suggest me some ideas so that i can solve these
> issues?
You need to give at least _some_ indication of your requirements --
what's on your file system, what is the expected pattern of access to
it, do you require write access all the time or only occasional updates
of the whole system, etc. ?
--
dwmw2
next prev parent reply other threads:[~2003-02-08 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 14:20 File systems in embedded devices Nandakumar NarayanaSwamy
2003-02-08 19:41 ` David Woodhouse [this message]
2003-02-09 10:03 Mikael Starvik
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=1044733282.2943.34.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanda_kn@rediffmail.com \
/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 NNTP newsgroup(s).