All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Therning <magnus-work@therning.org>
To: selinux@tycho.nsa.gov
Subject: Re: SELinux on Debian (Sid), second try
Date: Mon, 28 Jun 2004 11:42:30 +0200	[thread overview]
Message-ID: <20040628094230.GB1688@philips.com> (raw)
In-Reply-To: <200406251908.56334.russell@coker.com.au>

[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]

On Fri, Jun 25, 2004 at 07:08:56PM +1000, Russell Coker wrote:
>On Fri, 25 Jun 2004 02:39, Magnus Therning <magnus-work@therning.org> wrote:
>> Should they be installed in some specific order (i.e. SELinux packages
>> before the others, or the other way around)?
>>
>> Does it matter when I install the kernel with SELinux support?
>
>Install everything apart from selinux-policy-default and then boot the
>SE Linux kernel.  Then install selinux-policy-default last and reboot.

Everything goes well until I get to the selinux-policy-default package.
The version I get is 1:1.12-3 (from Sid). The installation ends with the
following:

make: *** /etc/selinux: No such file or directory.  Stop.
run-parts: /etc/dpkg/postinst.d/selinux exited with return code 2
"/bin/run-parts --arg=selinux-policy-default /etc/dpkg/postinst.d" failed: 256
dpkg: error processing selinux-policy-default (--configure):
 1Error running trigger postinst: No such file or directory
Errors were encountered while processing:
 selinux-policy-default
E: Sub-process /usr/bin/dpkg returned error code (1)


Indeed, there is no directory called /etc/selinux. When should it have
been created? (By what package?)

I've tried to keep track of all the steps I've taken, and all packages
that have been installed as a result of them, when trying to convert a
Sid system to SELinux. Let me know if you need any more info regarding
versions of packages and so on.

/M

>
>-- 
>http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
>http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
>http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
>http://www.coker.com.au/~russell/  My home page
>
>--
>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.

-- 
-----------------------------------------------------------------------
Magnus Therning                 Philips Research Laboratories Eindhoven
Phone: +31 40 2745179           (OpenPGP: 0x4FBB2C40)

You can't depend on your judgement when your imagination is out of focus.
     -- Mark Twain

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-28  9:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 16:39 SELinux on Debian (Sid), second try Magnus Therning
2004-06-25  9:08 ` Russell Coker
2004-06-28  9:42   ` Magnus Therning [this message]
2004-06-28 13:47     ` Russell Coker
2004-06-28 15:04       ` Magnus Therning
2004-06-29  5:33         ` Russell Coker
2004-06-29  8:59           ` Magnus Therning
2004-06-30  8:29             ` Magnus Therning
2004-06-30 20:22               ` Valdis.Kletnieks
2004-07-07 16:05               ` Stephen Smalley
2004-07-08  9:08                 ` Russell Coker

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=20040628094230.GB1688@philips.com \
    --to=magnus-work@therning.org \
    --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.