From: Michael Schuerig <michael.lists@schuerig.de>
To: linux-btrfs@vger.kernel.org
Subject: SELinux on btrfs
Date: Tue, 01 Apr 2014 16:50:38 +0200 [thread overview]
Message-ID: <5090808.sXhgbrHacY@fuchsia> (raw)
I'm currently considering to use SELinux on an existing system with
btrfs filesystems. This would be my first with SELinux and I wouldn't
expect everything to go smoothly. I'm already aware that SELinux's
automatic labelling of files is not aware of subvolumes[*]. I already
have quite a few read-only snapshots that I don't want to forfeit,
however, I'm not at all sure how SELinux would interact with them.
Are there any other considerations I ought to be aware of?
Michael
[*] https://wiki.debian.org/SELinux/Setup#btrfs
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
next reply other threads:[~2014-04-01 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 14:50 Michael Schuerig [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-12 16:15 SELinux on btrfs Chris Murphy
2014-04-30 8:01 ` Russell Coker
2014-04-30 16:04 ` Chris Murphy
2014-05-02 1:51 ` Russell Coker
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=5090808.sXhgbrHacY@fuchsia \
--to=michael.lists@schuerig.de \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox