From: Matthias Schniedermeyer <ms@citd.de>
To: Shawn <core@enodev.com>
Cc: "Leonardo H. Machado" <leoh@dcc.ufmg.br>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: cachefs on linux
Date: Mon, 9 Jun 2003 22:56:51 +0200 [thread overview]
Message-ID: <20030609205650.GA11518@citd.de> (raw)
In-Reply-To: <1055191776.13435.6.camel@localhost>
On Mon, Jun 09, 2003 at 03:49:36PM -0500, Shawn wrote:
> On Mon, 2003-06-09 at 15:42, Matthias Schniedermeyer wrote:
> > On Mon, Jun 09, 2003 at 04:26:01PM -0300, Leonardo H. Machado wrote:
> > > Why has Solaris a CacheFS file system, while linux doesn't?
> >
> > Is this a "You don't know it, you don't need it" thing?
> Well, it's a nice way to simulate writing on r/o filesystems IIRC. Like
> mounting a cdrom then writing to it, but you're not.
>
> Was that was this was? Anyway, linux also does not have unionFS. If it
> was that big of a deal, someone would write it. As it is, it's a
> whizbang no one cares about enough.
I remember this as "translucent"<whatever>.
IIRC you can do this with "bind"-mounting the writeable-dir over the
read-only dir, but that's from rusted memory, maybe i'm wrong.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2003-06-09 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 19:26 cachefs on linux Leonardo H. Machado
2003-06-09 20:42 ` Matthias Schniedermeyer
2003-06-09 20:49 ` Shawn
2003-06-09 20:56 ` Matthias Schniedermeyer [this message]
2003-06-10 8:29 ` Sean Hunter
2003-06-10 19:15 ` Rob Landley
2003-06-10 20:39 ` Anton Altaparmakov
2003-06-11 0:51 ` Rob Landley
2003-06-11 10:03 ` Bernd Eckenfels
2003-06-11 11:12 ` Hirokazu Takahashi
2003-06-11 22:26 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 7:53 john
2003-06-11 21:01 Perez-Gonzalez, Inaky
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=20030609205650.GA11518@citd.de \
--to=ms@citd.de \
--cc=core@enodev.com \
--cc=leoh@dcc.ufmg.br \
--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