From: "Oliver Fuchs" <olivers.lists@gmx.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Does ext2 based on MTD acceptable for Embedded Development?
Date: Fri, 27 Aug 2004 12:05:44 +0200 [thread overview]
Message-ID: <412F2398.313.E2BE91@localhost> (raw)
In-Reply-To: <20040827074002.58692C109F@atlas.denx.de>
From: Wolfgang Denk <wd@denx.de>
> > I would not use ext2 on MTD.
>
> We do, and it works perfect. You just want to make sure to mount it
> read-only.
Is there an advantage to use ext2 instead of cramfs for read only fs?
Regards,
Oliver
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-27 10:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 14:29 MPC82xx enet on SCC3 Oliver Fuchs
2004-08-12 16:55 ` Dan Malek
2004-08-16 14:00 ` Oliver Fuchs
2004-08-16 16:21 ` Wolfgang Denk
2004-08-16 17:40 ` Ralph Siemsen
2004-08-17 9:49 ` Oliver Fuchs
2004-08-26 10:08 ` Cramfs Limitations Song Sam
2004-08-26 15:12 ` Wolfgang Denk
2004-08-27 1:35 ` Song Sam
2004-08-27 7:38 ` Wolfgang Denk
2004-08-27 8:33 ` Song Sam
2004-08-26 10:10 ` Does ext2 based on MTD acceptable for Embedded Development? Song Sam
2004-08-27 7:08 ` Oliver Fuchs
2004-08-27 7:39 ` Wolfgang Denk
2004-08-27 10:05 ` Oliver Fuchs [this message]
2004-08-27 14:24 ` Wolfgang Denk
2004-08-16 18:18 ` MPC82xx enet on SCC3 Dan Malek
2004-08-17 9:49 ` Oliver Fuchs
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 6:56 Does ext2 based on MTD acceptable for Embedded Development? Rupesh S
2004-08-30 8:13 ` Wolfgang Denk
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=412F2398.313.E2BE91@localhost \
--to=olivers.lists@gmx.net \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.