All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: policy version jumped to 18
Date: Sat, 31 Jul 2004 13:06:34 +0100	[thread overview]
Message-ID: <20040731120634.GK3378@lkcl.net> (raw)

arg, wot a pain.

i am doing an install on another machine, just for fun
(and prior to doing an upgrade on another).

this is with my lovely 2.6.6-selinux1 kernel.

policy version being reported by the kernel i am using is 17.

checkpolicy is being a pain and reporting that it does version 18.

therefore, a make install does this:

creates a policy.conf file, and creates a .17 file (somewhere) because
that's what the kernel supports.

checkpolicy is then used to find what to check, which says "i do version 18".

consequently, i don't get anywhere.

hack-time...

-- 
-- 
Information I post is with honesty, integrity, and the expectation that
you will take full responsibility if acting on the information contained,
and that, should you find it to be flawed or even mildly useful, you
will act with both honesty and integrity in return - and tell me.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


--
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-07-31 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 12:06 Luke Kenneth Casson Leighton [this message]
2004-07-31 14:18 ` policy version jumped to 18 Luke Kenneth Casson Leighton
2004-07-31 16:11   ` Erich Schubert
2004-07-31 17:12     ` Luke Kenneth Casson Leighton
2004-08-02 12:34 ` 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=20040731120634.GK3378@lkcl.net \
    --to=lkcl@lkcl.net \
    --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.