public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Padraig Brady <padraig@antefacto.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ramdisk/tmpfs/ramfs/memfs ?
Date: Fri, 27 Apr 2001 16:56:35 +0100	[thread overview]
Message-ID: <15296.988386995@redhat.com> (raw)
In-Reply-To: <3AE99CE8.BD325F52@antefacto.com>
In-Reply-To: <3AE99CE8.BD325F52@antefacto.com>  <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se>


padraig@antefacto.com said:
> btw I get my initial root filesystem from a compact flash that can be
> accessed just like a hardisk. It's writeable also like a harddisk, but
> we boot with it readonly, and only mount it rw if we want to save
> config or whatever. We definitely wouldn't swap to it as it has
> limited erase/write cycles. The filesystem is compressed ext2.

Why copy it into RAM? Why not use cramfs and either turn the writable
directories into symlinks into a ramfs which you create at boot time, or 
union-mount a ramfs over the top of it?


padraig@antefacto.com said:
> As for using JFFS2 + MTD ramdisk intead of ext2+e2compr+ramdisk is not
> an option as the only advantage would be journalling, you still can't
> resize. IMHO JFFS is only required where you have flash without an IDE
> interface.

True. We are currently lacking a compact, compressing, journalling 
filesystem for use on block devices. It's been suggested that we could make 
JFFS2 work on them, by making a fake MTD device which uses a block device 
as backing store. Nobody's yet shown me the code though :)

--
dwmw2



  parent reply	other threads:[~2001-04-27 15:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 19:40 ramdisk/tmpfs/ramfs/memfs ? Padraig Brady
2001-04-26 18:48 ` Bjorn Wesen
2001-04-26 20:39   ` Marko Kreen
2001-04-27  0:37     ` H. Peter Anvin
2001-04-27 11:32       ` mirabilos
2001-04-27 13:41         ` Christoph Rohland
2001-04-26 20:49   ` H. Peter Anvin
2001-04-26 22:25     ` Ingo Oeser
2001-04-27  9:36   ` David Woodhouse
2001-04-27 11:36     ` mirabilos
2001-06-22  8:15     ` Padraig Brady
2001-04-27 15:56   ` David Woodhouse [this message]
2001-04-27 16:19     ` mirabilos
2001-04-27 17:39     ` David L. Parsley
2001-04-27 17:53     ` Padraig Brady
2001-04-27 17:23       ` Xavier Bestel
2001-04-28 10:30     ` David Woodhouse
2001-04-27 16:23   ` Padraig Brady
2001-04-27 14:31     ` Bjorn Wesen
2001-04-27 15:38     ` Christoph Rohland
2001-04-27  7:58 ` Christoph Rohland

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=15296.988386995@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=padraig@antefacto.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