From: Jeffrey Denton <dentonj@c2i2.com>
To: <john.rh@hushmail.com>
Cc: <SELinux@tycho.nsa.gov>
Subject: Re: Slackware
Date: Wed, 27 Jun 2001 05:21:49 -0700 (MST) [thread overview]
Message-ID: <0106270508380.3793-100000@localhost> (raw)
In-Reply-To: <200106270253.TAA31440@user7.hushmail.com>
On Tue, 26 Jun 2001 john.rh@hushmail.com wrote:
> Has there been much success in using SELinux with the Slackware distribution?
> Comments on using SELinux with Slackware are GREATLY appreciated!
It's on my long list of things I'd like to do. But I know that doesn't help...
=-)
I haven't seen any discussion about getting SElinux to work with Slackware on
this list ( a grep through the mail folder only turned up your email ). A query
on #slackware at openprojects.net didn't get a response. ( But that doesn't mean
anything. )
If anyone has ported SElinux to Slackware, they've kept it too themselves.
Considering that Slackware user's tend be independant and do-it-yourself types,
it wouldn't surprise me if someone has.
If you are interested in making the appropriate changes, I'd be willing to test
them.
Jeff
--
You have received this message because you are subscribed to the selinux 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:[~2001-06-27 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 0:42 Slackware john.rh
2001-06-27 12:21 ` Jeffrey Denton [this message]
2001-06-27 17:28 ` SuSE Milos Rancic
2001-06-27 20:27 ` SuSE Milos Rancic
2001-06-28 14:01 ` LIDS & MAC on Linux Zachary Uram
-- strict thread matches above, loose matches on Subject: below --
2001-06-27 13:37 Slackware Ward, Robert D
2001-06-27 14:15 ` Slackware Stephen Smalley
2001-06-27 15:29 Slackware john.rh
2018-10-04 22:27 Slackware cslater
2001-07-02 12:50 ` Slackware Stephen 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=0106270508380.3793-100000@localhost \
--to=dentonj@c2i2.com \
--cc=SELinux@tycho.nsa.gov \
--cc=john.rh@hushmail.com \
/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.