From: Claudio Martins <ctpm@rnl.ist.utl.pt>
To: linux-kernel@vger.kernel.org
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Ian Kent" <raven@themaw.net>, "Carsten Otte" <cotte@freenet.de>,
mszeredi@inf.bme.hu, herbert@13thfloor.at
Subject: Re: unionfs
Date: Mon, 15 Mar 2004 17:09:11 +0000 [thread overview]
Message-ID: <200403151709.11373.ctpm@rnl.ist.utl.pt> (raw)
In-Reply-To: <20040315161323.GD16615@wohnheim.fh-wedel.de>
On Monday 15 March 2004 16:13, Jörn Engel wrote:
> On Mon, 15 March 2004 22:35:20 +0800, Ian Kent wrote:
> > I don't understand the requirement properly. Sorry.
>
> Depends on who you ask, but imo it boils down to this:
> - Use one filesystem as backing store, usually ro.
> - Have another filesystem on top for extra functionality, usually rw
> access.
>
> Famous example is a rw-CDROM, where writes go to hard drive and
> unchanged data is read from CDROM. But it makes sense for other
> things as well.
If I understand correctly this unionfs feature would also be the cleanest
way of changing the root filesystem after using an initrd ramdisk on boot.
Currently the pivot_root call is used to change root but that still implies a
bit of a hack. You can read about it on this fine paper:
http://www.cis.udel.edu/~zhi/www.docshow.net/linux/ols.zip
It's also a good read if you want to understand the linux bootloaders and
the boot process in general.
Regards
Claudio
next prev parent reply other threads:[~2004-03-15 17:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 11:35 unionfs Carsten Otte
2004-03-15 12:19 ` unionfs Jörn Engel
2004-03-15 12:47 ` unionfs Ian Kent
2004-03-15 13:16 ` unionfs Jörn Engel
2004-03-15 14:35 ` unionfs Ian Kent
2004-03-15 16:13 ` unionfs Jörn Engel
2004-03-15 17:09 ` Claudio Martins [this message]
2004-03-15 19:22 ` unionfs Horst von Brand
2004-03-15 23:20 ` unionfs Chris Friesen
2004-03-16 16:04 ` unionfs Horst von Brand
2004-03-16 17:31 ` unionfs Jörn Engel
2004-03-16 18:04 ` unionfs Jörn Engel
2004-03-16 19:40 ` unionfs Horst von Brand
2004-03-16 20:45 ` unionfs Jörn Engel
2004-03-16 19:19 ` unionfs Horst von Brand
2004-03-16 20:00 ` unionfs Chris Friesen
2004-03-23 2:38 ` unionfs Robert White
2004-03-15 23:52 ` unionfs Jörn Engel
2004-03-16 16:18 ` unionfs Horst von Brand
2004-03-16 17:10 ` unionfs Jörn Engel
2004-03-19 9:11 ` unionfs Jamie Lokier
2004-03-19 9:42 ` unionfs Jörn Engel
2004-03-19 9:04 ` unionfs Jamie Lokier
2004-03-16 19:03 ` unionfs Andy Isaacson
2004-03-15 14:37 ` unionfs Ian Kent
2004-03-15 16:15 ` unionfs Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 9:52 unionfs Miklos Szeredi
2004-03-08 16:10 ` unionfs Bernd Schubert
2004-03-09 9:38 ` unionfs Miklos Szeredi
[not found] ` <20040311151343.GA943@escher.cs.wm.edu>
2004-03-11 15:44 ` unionfs Miklos Szeredi
2004-03-14 2:33 ` unionfs Ian Kent
2004-03-14 4:20 ` unionfs Horst von Brand
2004-03-16 12:42 ` unionfs Miklos Szeredi
[not found] ` <20040315214207.GA26615@escher.cs.wm.edu>
2004-03-16 13:43 ` unionfs Miklos Szeredi
2004-03-12 23:37 ` unionfs Herbert Poetzl
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=200403151709.11373.ctpm@rnl.ist.utl.pt \
--to=ctpm@rnl.ist.utl.pt \
--cc=cotte@freenet.de \
--cc=herbert@13thfloor.at \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@inf.bme.hu \
--cc=raven@themaw.net \
/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;
as well as URLs for NNTP newsgroup(s).