From: Thorsten Kukuk <kukuk@suse.de>
To: selinux@tycho.nsa.gov
Subject: Re: libselinux.so.1 and some utils shouldn't be in /usr
Date: Mon, 20 Oct 2003 17:37:20 +0200 [thread overview]
Message-ID: <20031020153720.GA29503@suse.de> (raw)
In-Reply-To: <20031020145526.H321@lemuria.org>
On Mon, Oct 20, Tom wrote:
> On Sun, Oct 19, 2003 at 06:35:01PM +0200, Bastian Blank wrote:
> > okay, i see it. but it seems to violate the fhs by put the libselinux.so
> > symlink into /lib as well, it is not essential for running applications.
>
> It is. For all apps that reside in /bin or /sbin and could potentially
> be executed before /usr is mounted.
Tom, don't be confused with the real library and the .so symlink.
The real library should be in /lib
The .so link, which is only used for linking applications against
this library and never for runtime, should reside in /usr/lib.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
--
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-10-20 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 11:34 libselinux.so.1 and some utils shouldn't be in /usr Bastian Blank
2003-10-18 14:35 ` Russell Coker
2003-10-19 12:10 ` Bastian Blank
2003-10-19 13:01 ` Russell Coker
2003-10-19 16:35 ` Bastian Blank
2003-10-20 12:55 ` Tom
2003-10-20 15:37 ` Thorsten Kukuk [this message]
2003-10-20 15:56 ` Stephen Smalley
2003-10-20 13:01 ` Stephen Smalley
2003-10-20 17:49 ` Bastian Blank
2003-10-20 18:06 ` 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=20031020153720.GA29503@suse.de \
--to=kukuk@suse.de \
--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.