public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: Marc Singer <elf@buici.com>
Cc: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>,
	mtd <linux-mtd@lists.infradead.org>
Subject: Re: Interest in DOC and YAFFS? --> YAFFS bootloading
Date: 24 Sep 2002 11:47:43 -0700	[thread overview]
Message-ID: <1032893263.21552.15.camel@timmy> (raw)
In-Reply-To: <20020924183704.GB3074@buici.com>

> > cramfs is a read only filesystem not an archive format like zip or tar
> > so you do not have to copy the data into another filesystem to use it.
> > You use cramfs instead of initrd+filesystem.
> 
> That isn't really the issue here.  We're talking about using gzip'd
> ext2 versus cramfs to do initrd.  The thing is that in my tests,
> cramfs images are larger than compressed ext2 images.  Not what I
> would expect.

if you are talking about an initrd, then the features of cramfs aren't
quite as usefull, as the whole thing will be loaded into ram anyway. On
the other side:

A cramfs will always be exactly as small as it needs to be, no guessing
on an image size. cramfs is created by population, not by making an
image, formatting it, mounting it loopback, and then copying files.

incedentally, I have a copy of mkcramfs with device table support (as
seen in mkfs.jffs2) as well as permission squashing, so that a cramfs
image can be made withoutt root (complete with suid root programs, and
/dev entries)

  reply	other threads:[~2002-09-24 18:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23  9:20 jffs2 and Doc 2000 eylon eyal
2002-09-24  0:03 ` Interest in DOC and YAFFS? Charles Manning
2002-09-24  3:44   ` Marc Singer
2002-09-24  3:58     ` Interest in DOC and YAFFS? --> YAFFS bootloading Charles Manning
2002-09-24  4:44       ` Marc Singer
2002-09-24  7:53         ` Russ Dill
2002-09-24 16:53           ` Marc Singer
2002-09-24 16:59             ` Russ Dill
2002-09-24 17:14               ` Marc Singer
2002-09-24 17:21                 ` Brian J. Fox
2002-09-24 17:30                 ` Russ Dill
2002-09-24 18:33                   ` Marc Singer
2002-09-24 17:44                 ` Kenneth Johansson
2002-09-24 18:37                   ` Marc Singer
2002-09-24 18:47                     ` Russ Dill [this message]
2002-09-24 20:22                       ` Marc Singer
2002-09-24 20:41                         ` Russ Dill
2002-09-24  7:23       ` Nick Bane
2002-09-24 16:55         ` Marc Singer
2002-09-24 18:23           ` Nick Bane
2002-09-24 20:53             ` Interest in DOC and YAFFS? Charles Manning
2002-09-24 22:46               ` Christian Gan
2002-09-25  7:33                 ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2002-09-25  7:09 Interest in DOC and YAFFS? --> YAFFS bootloading Srinivasan.Ramasubramaniam
2002-09-25  8:38 ` Russ Dill
2002-09-25 13:34   ` Henrik Nordström
2002-09-25 16:34     ` Russ Dill

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=1032893263.21552.15.camel@timmy \
    --to=russ.dill@asu.edu \
    --cc=elf@buici.com \
    --cc=kenneth.johansson@etx.ericsson.se \
    --cc=linux-mtd@lists.infradead.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