From: Amit D Chaudhary <amit@muppetlabs.com>
To: Bjorn Wesen <bjorn@sparta.lu.se>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: CRAMFS
Date: Fri, 23 Mar 2001 14:01:54 -0800 [thread overview]
Message-ID: <3ABBC7D2.6070502@muppetlabs.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010323194500.14171C-100000@medusa.sparta.lu.se>
> I don't know why the comparision is made though, they are used for two
> completely different things... ramfs is for temporary file storage, cramfs
> is for immutable files stored on flash. Each by itself is quite optimal
> for what it's designed for, isn't it ?
Exactly. My mistake earlier to assume cramfs was "compressed ramfs"! ;-)
I should compare it to the tar.gz option and JFFS2. Will do in the next
evaluation.
This will be more of a replace initrd+custom /linuxrc with a
CRAMFS-based rootfs on a flash device assuming CRAMFS can be directly
read by kernel\init for getting the rootfs. Ditto for JFFS2
Also, the platform is PPC, IBM 405GP to be precise.
Regards
Amit
next prev parent reply other threads:[~2001-03-23 21:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 6:36 /linuxrc query Amit D Chaudhary
2001-03-23 6:51 ` Werner Almesberger
2001-03-23 7:00 ` Amit D Chaudhary
2001-03-23 11:18 ` Werner Almesberger
2001-03-23 17:46 ` Amit D Chaudhary
2001-03-23 7:07 ` Amit D Chaudhary
2001-03-23 11:24 ` Werner Almesberger
2001-03-23 14:07 ` David Woodhouse
2001-03-23 18:00 ` RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) Amit D Chaudhary
2001-03-23 19:37 ` David Woodhouse
2001-03-23 20:25 ` CRAMFS Bjorn Wesen
2001-03-23 22:01 ` Amit D Chaudhary [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-09 4:24 cramfs Trever L. Adams
2001-07-16 6:23 ` cramfs Daniel Quinlan
2003-11-07 20:07 CRAMFS Bradley Bozarth
2003-11-09 15:15 ` CRAMFS H. Peter Anvin
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=3ABBC7D2.6070502@muppetlabs.com \
--to=amit@muppetlabs.com \
--cc=bjorn@sparta.lu.se \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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