From: Jaspreet Singh <jsingh@ensim.com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Dale Amon <amon@vnl.com>, Erich Schubert <erich@debian.org>,
Stephen Smalley <sds@epoch.ncsc.mil>, nsa <SELinux@tycho.nsa.gov>
Subject: Re: Overlay Filesystem and SELinux
Date: Mon, 27 Dec 2004 16:29:33 +0530 [thread overview]
Message-ID: <1104145173.20250.2.camel@jsingh> (raw)
In-Reply-To: <20041227102704.GB6750@lkcl.net>
Hi Luke,
On Mon, 2004-12-27 at 10:27 +0000, Luke Kenneth Casson Leighton wrote:
> are the knoppix team aware of it?
>
well no ... I am in touch with Tomas Matejicek of www.linux-live.org I
think i would mail and check response. Anyone in touch with them ???
I am studying selinux implementation in 2.6 kernels .. anyone with
revelent docs .. the one on nsa website is stale.
Thanx,
Jaspreet
> On Mon, Dec 27, 2004 at 12:09:10AM +0530, Jaspreet Singh wrote:
>
> > Hi,
> >
> > On Sun, 2004-12-26 at 12:54 +0000, Dale Amon wrote:
> > > > 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.
> > >
> > > Brilliant. I have been waiting for this quite literally
> > > for years. What are the chances it will go into the
> > > main kernel tree?
> >
> > Thanx :) , Yes the official maintainers can answer that question better.
> > For all i know unionfs is been publicized at lkml and there are talks
> > for the same.
> >
> > Till recently, it just seemed to be an academic project. But now it has
> > gained momentum. I have used and extended 3 overlay file-systems .. and
> > this one seemed to be most promising and stable.
> >
> > It has some very good features like - adding/removing branches (i.e
> > directories ) from a union.
> >
> > But, i am just a fresh grad .. probably people out there and judge this
> > file-system better.
> >
> > Currently my port works on 2.6.0 -to- 2.6.9 kernels .. but maintainers
> > are reviewing it .. would work on it.
> >
> > Thanx,
> > 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.
>
--
--
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-27 10:59 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
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 [this message]
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=1104145173.20250.2.camel@jsingh \
--to=jsingh@ensim.com \
--cc=SELinux@tycho.nsa.gov \
--cc=amon@vnl.com \
--cc=erich@debian.org \
--cc=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
/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.