From: "Wolfgang Weisselberg" <uzx87lvfmukwc001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read-only media in a LVM?
Date: Mon Jun 23 19:35:02 2003 [thread overview]
Message-ID: <6805-61260@sneakemail.com> (raw)
In-Reply-To: <C42D120999B1CC4C886B6BB2832F356019BF90@hermes.genomatica.com>
Sean P. Kane wrote 78 lines:
> I'd love to have a unionfs, but my understanding is that no such beast
> exists for Linux 2.4 currently
Try looking at
http://plasticfs.sourceforge.net/plasticfs.html
Plasticfs-viewpath is basically a unionof all filesystems in
the viewpath, changes happen on the first one and a .whiteout
remembers what you deleted. It does *not* work for root
(security!!! You do not want root to see /tmp/login instead of
/bin/login!). Remember to set the environment variables, e.g.
LD_PRELOAD=/usr/local/lib/libplasticfs.so
PLASTICFS="viewpath /ramdisk /cdrom1 /cdrom2"
/bin/bash # or whatever program you want.
Since Plasticfs works on file-level, you should be able to mix
and match filesystems as you like. Note however that --- since
we just overload common FS access methods --- some things might
not work.
I have it in production use (for Aegis, not for cdroms).
-Wolfgang
next prev parent reply other threads:[~2003-06-23 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 17:13 [linux-lvm] read-only media in a LVM? Sean P. Kane
2003-06-23 17:41 ` Kevin P. Fleming
2003-06-23 18:54 ` Sean P. Kane
2003-06-23 19:35 ` Wolfgang Weisselberg [this message]
2003-06-23 20:10 ` Kevin P. Fleming
-- strict thread matches above, loose matches on Subject: below --
2003-06-24 18:49 Sean P. Kane
2003-06-24 11:27 Sean P. Kane
2003-06-23 12:51 Sean P. Kane
2003-06-23 16:23 ` Wolfgang Weisselberg
2003-06-16 8:35 Sean P. Kane
2003-06-16 8:52 ` Joe Thornber
2002-05-27 18:30 Ami Fischman
2002-05-28 3:40 ` Joe Thornber
2002-05-28 3:44 ` Joe Thornber
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=6805-61260@sneakemail.com \
--to=uzx87lvfmukwc001@sneakemail.com \
--cc=linux-lvm@sistina.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