From: Jaspreet Singh <jsingh@ensim.com>
To: Erich Schubert <erich@debian.org>
Cc: nsa <SELinux@tycho.nsa.gov>
Subject: Re: Overlay Filesystem and SELinux
Date: Sun, 26 Dec 2004 14:11:00 +0530 [thread overview]
Message-ID: <1104050461.14672.6.camel@jsingh> (raw)
In-Reply-To: <1104022405.29054.7.camel@wintermute.xmldesign.de>
Hi,
I was initially involved in creating a unionfs (of BSD) for Linux. This
project was called "mini_fo". Search google for results.
That project is now .. not maintained .. and now I am involved in a much
more sophisticated implementation called - "unionfs" . Check this link -
www.fsl.cs.sunysb.edu/project-unionfs.html
Unionfs was initially only for 2.4 kernel, but i recently ported it to
2.6. The port is not official yet. But, its working.
> I'd love to use your overlay-fs when I needed to setup some virtual
> boxes. This is a great tool for virtualization. You can use this to
> manage a group of virtual hosts more easily (for example installing new
> software on them or upgrading existing)
> Do you also have some "hiding" features? With your concept right now,
> none of the overlayed files can be deleted. Or do you have a way of
> signalling that?
>
Yups, it has all BSD unionfs/union-mount features. My 2.6 port is not
selinux compatible yet .. but would be in some time.
> How do you create the whole path? just by doing a number of mkdirs? IMHO
> you should copy the xattr attributes from the overlayed directories
> here. As long as you are inside the kernel, doing so shouldn't be too
> hard.
>
nope .. just union mount some already mounted directories(called
branches) on a mount point and then any lookups/writes on mount-points
would follow COW semantics. And changes would be written to the topmost
RW branch.
Howz it.
Greetings and Mary Christmas,
Jaspreet
--
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-12-26 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 12:10 Virtualization and SELinux Jaspreet Singh
2004-10-20 15:10 ` Luke Kenneth Casson Leighton
2004-10-20 17:49 ` Luke Kenneth Casson Leighton
2004-10-27 14:32 ` Overlay Filesystem " Jaspreet Singh
[not found] ` <1104022405.29054.7.camel@wintermute.xmldesign.de>
2004-12-26 8:41 ` Jaspreet Singh [this message]
2004-12-26 12:54 ` Dale Amon
2004-12-26 18:39 ` Jaspreet Singh
[not found] ` <20041227102704.GB6750@lkcl.net>
2004-12-27 10:59 ` Jaspreet Singh
2004-12-30 18:04 ` Dale Amon
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=1104050461.14672.6.camel@jsingh \
--to=jsingh@ensim.com \
--cc=SELinux@tycho.nsa.gov \
--cc=erich@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.