From: Matthew Cengia <mattcen@cyber.com.au>
To: linux-unionfs@vger.kernel.org
Subject: Fwd: overlayfs+selinux error: OPNOTSUPP
Date: Mon, 21 Sep 2015 17:43:35 +1000 [thread overview]
Message-ID: <20150921074335.GI22582@cyber.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Hi all,
I've posted a message to LKML on Friday, and subsequently, upon
recommendation, have posted to the SELinux list, but then I stumbled
upon this list, which seems to have at least semi-relevent discussion on
SELinux/overlay interactions. I'd really appreciate if you folks could
have a look at my post (https://lkml.org/lkml/2015/9/17/888) to see if
it's anything you're able to help with; I'm running out of ideas!
----- Forwarded message from Matthew Cengia <mattcen@cyber.com.au> -----
> Date: Fri, 18 Sep 2015 12:07:43 +1000
> From: Matthew Cengia <mattcen@cyber.com.au>
> To: linux-kernel@vger.kernel.org
> Cc: Matthew Cengia <mattcen@gmail.com>, "Trent W. Buck" <twb@cyber.com.au>
> Subject: overlayfs+selinux error: OPNOTSUPP
> Message-ID: <20150918020743.GC22582@cyber.com.au>
> User-Agent: Mutt/1.5.21 (2010-09-15)
>
> Hi all,
>
> Please CC me directly when responding, as I'm not subscribed to the
> mailing list.
>
>
> Summary
> -------
> I deploy diskless Debian kiosks in prisons, for use by inmates.
> As part of the Debian 7 to 8 upgrade, I want to enable SELinux.
> My initrd uses overlayfs to combine a ro squashfs and a rw tmpfs.
>
> When I add SELinux into the mix, I get a lot of EOPNOTSUPP.
[...]
----- End forwarded message -----
--
Regards,
Matthew Cengia
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next reply other threads:[~2015-09-21 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 7:43 Matthew Cengia [this message]
2015-09-21 14:34 ` Fwd: overlayfs+selinux error: OPNOTSUPP J. R. Okajima
2015-09-21 23:50 ` Matthew Cengia
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=20150921074335.GI22582@cyber.com.au \
--to=mattcen@cyber.com.au \
--cc=linux-unionfs@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 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.