All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Savage <savages@pcez.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: New security policy
Date: Mon, 10 Dec 2001 09:17:08 -0800	[thread overview]
Message-ID: <3C14EE14.1090505@pcez.com> (raw)
In-Reply-To: Pine.GSO.4.33.0112101059130.13300-100000@raven

Stephen Smalley wrote:

>On Sun, 9 Dec 2001, Shaun Savage wrote:
>
>>I have compiled some of the selinux utils for RH7.2, I hope to do the
>>rest this week.
>>this is how I did it
>>
>>I first did  >rpm -bp XXXX.spec
>>the patched the XXXX directory using the patch
>>on some XXXX i needed to autoconf  (caution: the autoconf that comes
>>with RH7.2 is bad upgrade to 2.52 from GNU.org)
>>I then go back to the SPEC directory and rpm -bc --short-circuit XXXX.spec
>>then rpm -bi --short-circuit XXXX.spec
>>
>
>In our work in upgrading the utilities, we've encountered a fair number of
>rejects from the existing patches that have required manual merging, and
>at least some of those manual merges were non-trivial.  We also had to add
>stat64 variants of the stat_secure system calls, with transparent
>redirection, in order to support the new fileutils package.  Are you
>actually dealing with any of these kinds of issues in your patches?
>
I entered most of patches by hand,  I thought most the manual patches 
easy.  The issue of stat_secure calls with transparent redirection,  I 
don't know.  I have only working on selinux for about 3 days.  I want to 
get the support programs ported first.  If you want I can make RPM's.  

Shaun Savage





--
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.

      reply	other threads:[~2001-12-10 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10  5:35 New security policy Shaun Savage
2001-12-10 15:49 ` Stephen Smalley
2001-12-10 16:44   ` Shaun Savage
2001-12-10 17:26     ` Stephen Smalley
2001-12-10 16:02 ` Stephen Smalley
2001-12-10 17:17   ` Shaun Savage [this message]

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=3C14EE14.1090505@pcez.com \
    --to=savages@pcez.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=sds@tislabs.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.