From: David Updegraff <dave@cray.com>
To: robin.gilks@tait.co.nz (Robin Gilks)
Cc: linuxppc-embedded@lists.linuxppc.org (linuxppc embedded)
Subject: Re: CRAMFS or SQUASHFS
Date: Tue, 3 Jun 2003 18:39:37 -0500 (CDT) [thread overview]
Message-ID: <200306032339.SAA37882@engcafe.us.cray.com> (raw)
In-Reply-To: <3EDD296F.FA278C9C@tait.co.nz> from "Robin Gilks" at Jun 04, 2003 11:04:15 AM
We ended up with squashfs since it gave better compression, better runtime
performance, and -- most importantly for us -- the 'mksquashfs' suite is
easy to compile up on non-Linux unixes, and it handles endiannes issues.
>
>
> Greetings
>
> I've been trying to determine the best Flash based *_read-only_* compressed
> filesystem for an embedded system.
>
> I can find nothing about CRAMFS - not even what it stands for - is it CRAM as in
> squeeze it all in or Compressed RAM meaning it uses loads of RAM to expand into.
> Just a hint in the right direction here would help!!
>
> For SQUASHFS, I'm unsure as to how mature it is and what its memory overhead is
> since its using zlib - would the discussions about sharing zlib workspace be
> relevant here as well?
>
> Does anyone have a horror story particular to either of these technologies?
>
> Many thanks...
>
> --
> Robin Gilks
> Senior Design Engineer Phone: (+64)(3) 357 1569
> Tait Electronics Fax : (+64)(3) 359 4632
> PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz
> New Zealand
>
>
>
--
Dave Updegraff, Cray Inc. / dave@cray.com / 218-525-1154
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-03 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 23:04 CRAMFS or SQUASHFS Robin Gilks
2003-06-03 23:39 ` David Updegraff [this message]
2003-06-04 0:31 ` Eugene Surovegin
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=200306032339.SAA37882@engcafe.us.cray.com \
--to=dave@cray.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=robin.gilks@tait.co.nz \
/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).