mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Art Boulatov <art@ksu.ru>, linux-kernel@vger.kernel.org
Subject: Re: filesystem for initrd
Date: Mon, 12 Mar 2001 14:51:46 +0100	[thread overview]
Message-ID: <20010312145146.A878@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3AAAC179.8020109@ksu.ru> <3AAAC6C5.EF198D4A@mandrakesoft.com>
In-Reply-To: <3AAAC6C5.EF198D4A@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sat, Mar 10, 2001 at 07:28:53PM -0500

On Sat, Mar 10, 2001 at 07:28:53PM -0500, Jeff Garzik wrote:
> cramfs is nice but still read-only at the moment...  You might be able
> to get away with stacking ramfs on top of that. 

What is easier because this ...

> If not, it shouldn't be hard to modify cramfs so that it allows
> fs modifications...  just stick the updated pages in RAM until
> the file is unlinked or the fs is unmounted.

... will lead into problems accounting available space on the fs,
since openers don't expect that they cannot write to a file
anymore, just because we we are out of RAM for backing the
writes.

I think unionfs will care for this kind of problems once we have
it implemented in an official tree.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<       come and join the fun       >>>>>>>>>>>>

      reply	other threads:[~2001-03-12 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-11  0:06 Art Boulatov
2001-03-11  0:28 ` Jeff Garzik
2001-03-12 13:51   ` Ingo Oeser [this message]

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=20010312145146.A878@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=art@ksu.ru \
    --cc=jgarzik@mandrakesoft.com \
    --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

all inboxes | Powered by JetHome®