From: Daniel J Walsh <dwalsh@redhat.com>
To: gyurdiev@redhat.com, Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: libsemod????
Date: Fri, 08 Jul 2005 12:49:34 -0400 [thread overview]
Message-ID: <42CEAE9E.5090902@redhat.com> (raw)
In-Reply-To: <1120833363.17407.30.camel@celtics.boston.redhat.com>
Why are we creating more libraries? What benefit does the added
complexity give us? Why not just have one library for policy file
management and one for selinux management? A developer using these
libraries in the future is not going to care about selinux/sepol/semod.
He wants to build an selinux aware app he will probably want to link to
libselinux.
ls -l /lib/libse*
-rwxr-xr-x 1 root root 77192 Jun 29 16:08 /lib/libselinux.so.1
-rwxr-xr-x 1 root root 135140 Jul 7 07:15 /lib/libsepol.so.1
Are these libraries too large. I do not want to add additional packages
just for libraries.
--
--
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 parent reply other threads:[~2005-07-08 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1120744424.514.23.camel@celtics.boston.redhat.com>
[not found] ` <1120826367.19035.26.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1120830443.17407.15.camel@celtics.boston.redhat.com>
[not found] ` <1120831505.19035.70.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1120833363.17407.30.camel@celtics.boston.redhat.com>
2005-07-08 16:49 ` Daniel J Walsh [this message]
2005-07-08 19:28 ` libsemod???? Karl MacMillan
2005-07-11 14:01 ` libsemod???? Stephen Smalley
2005-07-11 15:20 ` libsemod???? 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=42CEAE9E.5090902@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=gyurdiev@redhat.com \
--cc=sds@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.