All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Colin Walters <walters@verbum.org>
Cc: Dale Amon <amon@vnl.com>, Russell Coker <russell@coker.com.au>,
	selinux@tycho.nsa.gov
Subject: Re: Attn Colin: Overhelpful /usr/sbin/policy-remove-unwanted
Date: Mon, 1 Mar 2004 09:43:13 +0000	[thread overview]
Message-ID: <20040301094313.GB4168@vnl.com> (raw)
In-Reply-To: <1078117604.397.6.camel@nexus.verbum.private>

On Mon, Mar 01, 2004 at 12:06:45AM -0500, Colin Walters wrote:
> > After Colin's install script removes klogd.te, the policy build fails:
> 
> Are you using my very old selinux-policy-default package?  You must be,
> since Russell hasn't yet merged the smarter installation script into his
> packages.  Anyways at this point, I strongly suggest using Russell's
> policy packages.  Hopefully soon we'll get that script merged in.

I have to have your script to do what I'm doing. It's
not an issue of 'just instaling' selinux. I can do that.
It's the hands-off build I've been fiddling with for
some time. 

I've got a workaround for now, I just replace klogd.te after
the install 'Automatic' removes it. If you'd let me know when
the merge with your script occurs, I'd appreciate that greatly
as then I can back out the hacks I'm using and perhaps switch
entirely to Russ's repository.

Just so you know, this is what I have to do at present
to get a workable set for a hands-off build:

sources.list
--------------------
deb http://www.coker.com.au/newselinux/ ./
deb http://web.verbum.org/debian/ ./experimental/
deb http://ftp.nl.debian.org/debian/ sid main non-free contrib
deb http://ftp.nl.debian.org/debian-non-US sid/non-US main contrib non-free

preferences
--------------------
Package: *
Pin: release l=etbe
Pin-Priority: 1200

Package: *
Pin: release o=walters
Pin-Priority: 1100
 
If you or Russ think the problems are sorted, I'd be
happy to have a go at building entirely off his repository.
Note that I've not gotten around to switching over from
initrd to svinit boot procedures though. I'm doing this
as a background task as I'm quite busy with a job
right now. I just start up a test run of my autobuild
and go do real work for the next hour or two :-)

-- 
------------------------------------------------------
   Dale Amon     amon@islandone.org    +44-7802-188325
       International linux systems consultancy
     Hardware & software system design, security
    and networking, systems programming and Admin
	      "Have Laptop, Will Travel"
------------------------------------------------------

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

      reply	other threads:[~2004-03-01  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 18:14 Attn Colin: Overhelpful /usr/sbin/policy-remove-unwanted Dale Amon
2004-02-29  2:44 ` Russell Coker
2004-02-29  4:21   ` Dale Amon
2004-02-29  4:26   ` Dale Amon
2004-02-29  4:45     ` Russell Coker
2004-02-29 16:01       ` Dale Amon
2004-02-29 18:03         ` Russell Coker
2004-03-01  5:06         ` Colin Walters
2004-03-01  9:43           ` Dale Amon [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=20040301094313.GB4168@vnl.com \
    --to=amon@vnl.com \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    --cc=walters@verbum.org \
    /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.