From: Chris Vanden Berghe <vbc@zurich.ibm.com>
To: selinux@tycho.nsa.gov
Subject: Re: selinux-policy-default
Date: Wed, 03 Dec 2003 13:22:49 +0100 [thread overview]
Message-ID: <3FCDD599.4090402@zurich.ibm.com> (raw)
In-Reply-To: <200312030537.34475.russell@coker.com.au>
Hi,
>>I don't have '/usr/share/selinux/policy/current/' either, but I do have
>>'/usr/share/selinux/policy/default/'. Should I link /etc/selinux to
>>this '.../default/' dir?
>>
>>
>
>No. Copy what you want from the default directory to the current directory
>then make a symlink. Having the symlink point to the default directory won't
>do any good.
>
Tnx, this worked.
I'd be happy to do some testing if you have a new version of the
selinux-policy-default package available that addresses this issue.
Cheers,
Chris.
--
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-12-03 12:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 12:18 selinux-policy-default Chris Vanden Berghe
2003-12-02 13:56 ` selinux-policy-default Tom
2003-12-02 14:41 ` selinux-policy-default Chris Vanden Berghe
2003-12-02 15:24 ` selinux-policy-default Tom
2003-12-02 14:59 ` selinux-policy-default Russell Coker
2003-12-02 15:24 ` selinux-policy-default Chris Vanden Berghe
2003-12-02 18:37 ` selinux-policy-default Russell Coker
2003-12-03 12:22 ` Chris Vanden Berghe [this message]
2003-12-02 18:54 ` selinux-policy-default Tom
2003-12-02 15:04 ` selinux-policy-default Dale Amon
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 5:57 selinux-policy-default Eric Estabrooks
2004-02-06 10:31 ` selinux-policy-default Tomas Hoger
2004-02-06 13:01 ` selinux-policy-default Russell Coker
2004-02-06 12:39 ` selinux-policy-default Russell Coker
2004-02-06 15:09 ` selinux-policy-default Daniel J Walsh
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=3FCDD599.4090402@zurich.ibm.com \
--to=vbc@zurich.ibm.com \
--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.