From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: /proc woes
Date: Tue, 8 Oct 2002 16:32:46 +0200 [thread overview]
Message-ID: <20021008163245.A5508@lemuria.org> (raw)
Forget my last posting. I noticed a few seconds after pressing send
that of course all that is no good because /proc is not a supported
filesystem.
So instead of having a patch, I have a question: My /proc is file_t:
dr-xr-xr-x root root system_u:object_r:file_t proc
Doing a chcon manually fails:
# chcon system_u:object_r:proc_t /proc
chcon: /proc: Permission denied
So, what went wrong and what can I do to fix it?
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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 reply other threads:[~2002-10-08 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 14:32 Tom [this message]
2002-10-08 14:40 ` /proc woes Stephen Smalley
2002-10-08 15:11 ` Tom
2002-10-08 17:13 ` Russell Coker
2002-10-09 10:30 ` Tom
2002-10-08 18:43 ` Stephen Smalley
2002-10-08 19:29 ` Tom
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=20021008163245.A5508@lemuria.org \
--to=tom@lemuria.org \
--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.