All of lore.kernel.org
 help / color / mirror / Atom feed
From: Howard Holm <hdholm@epoch.ncsc.mil>
To: Colin Walters <walters@verbum.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: default policy package
Date: 03 Nov 2003 15:04:15 -0500	[thread overview]
Message-ID: <1067889855.29084.17.camel@moss-huskies> (raw)
In-Reply-To: <1067887630.24100.8.camel@metropolis.verbum.private>

On Mon, 2003-11-03 at 14:27, Colin Walters wrote:
> On Mon, 2003-11-03 at 11:48, Russell Coker wrote:
> 
> > Thanks for that reference, I have run check-all and fixed bugs in my policy 
> > tree related to updfstab, kudzu, and netsaint.  Colin, I have found what 
> > appears to be a minor bug in check-all, I get the following error related to 
> > mount:
> > 
> > Testing authbind.te...
> > Testing authbind.te...success.
> > make[1]: *** No rule to make target `presymlink/mount.te', needed by 
> > `presymlink/automount.te'.  Stop.
> 
> This is due to the fact that automount.te has a Depends: mount.te, but
> this is unnecessary since mount.te is included in the core
> (non-optional) policy.  Deleting that Depends: line should make it work.
> I'll try to come up with a patch soonish to make Depends: on core policy
> work though.

The Depends line has been fixed for a while (at least since the last
release) in the example policy at nsa.gov.  I've been using make
check-all for a while.  It's very useful, but it has some strange
behaviors.  I've noticed that often I can run check-all on a broken
policy and it will run fine.  Running it a second or third time will
cause the error to be generated.  Running make checkunused/file.te seems
to work in a more deterministic way.  I haven't had a chance to try and
track down the problem with check-all though.

-- 
Howard Holm <hdholm@epoch.ncsc.mil>
Office of Defensive Computing Research
National Security Agency


--
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:[~2003-11-03 20:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 11:43 default policy package Dale Amon
2003-11-03 13:38 ` Diyab
     [not found]   ` <200311040140.04077.russell@coker.com.au>
2003-11-03 15:05     ` Diyab
2003-11-03 15:29     ` Dale Amon
2003-11-03 16:18       ` Stephen Smalley
     [not found]         ` <200311040348.39876.russell@coker.com.au>
2003-11-03 19:27           ` Colin Walters
2003-11-03 20:04             ` Howard Holm [this message]
2003-11-03 20:11   ` Howard Holm
     [not found] ` <200311040115.57564.russell@coker.com.au>
2003-11-03 15:27   ` Dale Amon
2003-11-03 16:15     ` Stephen Smalley
2003-11-03 17:37       ` Dale Amon
2003-11-04 17:54         ` Dale Amon

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=1067889855.29084.17.camel@moss-huskies \
    --to=hdholm@epoch.ncsc.mil \
    --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.