From: Carsten Grohmann <carsten.grohmann@raumbildsysteme.de>
To: Russell Coker <russell@coker.com.au>, selinux@tycho.nsa.gov
Subject: Re: tmpfs_t
Date: Mon, 27 Jan 2003 12:16:50 +0100 [thread overview]
Message-ID: <200301271216.50369.carsten.grohmann@raumbildsysteme.de> (raw)
In-Reply-To: <200301251657.08983.russell@coker.com.au>
Am Samstag, 25. Januar 2003 16:57 schrieb Russell Coker:
> Or should I instead leave the tmpfs filesystem labelled as tmpfs_t
> and add appropriate file_type_auto_trans() rules for it?
.. a new xxx_tmpfs_t type and both add to the tmp_domain macro?
This way seems to be easy and good way.
--
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:[~2003-01-27 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 15:57 tmpfs_t Russell Coker
2003-01-27 11:16 ` Carsten Grohmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-27 13:20 tmpfs_t Stephen D. Smalley
2003-02-01 22:51 ` tmpfs_t Russell Coker
2003-02-04 18:36 tmpfs_t Stephen D. Smalley
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=200301271216.50369.carsten.grohmann@raumbildsysteme.de \
--to=carsten.grohmann@raumbildsysteme.de \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.