public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Konstantinos Agouros <elwood@agouros.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SELinux change from 2005.1 to 2006.1 policy update fails
Date: Wed, 20 Jun 2007 16:03:13 +0000 (UTC)	[thread overview]
Message-ID: <1182355393.900282@rumba> (raw)
In-Reply-To: 200706191845.39612.michaelkintzios@gmail.com

In <200706191845.39612.michaelkintzios@gmail.com> michaelkintzios@gmail.com (Mick) writes:

>--nextPart1695717.Xy3eqH9OGj
>Content-Type: text/plain;
>  charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: inline

>On Monday 18 June 2007 20:38, Konstantinos Agouros wrote:
>> In <200706180838.05681.michaelkintzios@gmail.com> michaelkintzios@gmail.c=
>om=20
>(Mick) writes:

>> >On Sunday 17 June 2007 12:22, Konstantinos Agouros wrote:
>> >> Hi,
>> >>
>> >> I tried upgrading from the 2005.1 to the 2006.1 profile. Updating
>> >>
>> >> selinux-base-policy-20070329 fails with the following message:
>> >> >>> Setting SELinux security labels
>> >> /etc/selinux/targeted/contexts/files/file_contexts: No such file or
>> >> directory
>> >
>> >What is listed under /etc/selinux/targeted/contexts/files/ ?
>>
>> /etc/selinux is empty.
>>
>> When I started with hardened sources this was all put to
>> /etc/security/selinux so it seems I need some kind of migration script or
>> is a simple
>> softlink good enough?

>Sorry Konstantin, last time I used SELinux for a very short time was more t=
>han=20
>three years ago . . . I've forgotten most of it since then and things most=
>=20
>likely have moved on.  Perhaps someone more versed in SELinux could help=20
>here?
>>
>> >If the file is there then can you check that you are not emerging this
>> > whil=3D e=3D20
>> >using FEATURES=3D3D"userpriv" in your make.conf.

>Aargh!  Why was my previous message received like so "whil=3D e=3D20"? What=
> email=20
>client are you using?
I have the mailinglist transferred to a local news server and use good old
nn as newsreader, which does not seem to cope well with utf-8 as transfer
encoding \:)

Cheers,

Konstantin
>=2D-=20
>Regards,
>Mick

>--nextPart1695717.Xy3eqH9OGj
>Content-Type: application/pgp-signature

>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.7 (GNU/Linux)

>iD8DBQBGeBZD5Fp0QerLYPcRAqFfAJ9YDDvz8jCwv1m7ZyjlQKC0mg37MwCeIGEl
>nCbzxef2UoZKpXXTj15z+Xo=
>=tjIP
>-----END PGP SIGNATURE-----

>--nextPart1695717.Xy3eqH9OGj--
>-- 
>gentoo-user@gentoo.org mailing list

-- 
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: elwood@agouros.de
Otkerstr. 28, 81547 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"Captain, this ship will not survive the forming of the cosmos." B'Elana Torres
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2007-06-20 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 11:22 [gentoo-user] SELinux change from 2005.1 to 2006.1 policy update fails Konstantinos Agouros
2007-06-18  7:38 ` Mick
2007-06-18 19:38   ` Konstantinos Agouros
2007-06-19 17:45     ` Mick
2007-06-20 16:03       ` Konstantinos Agouros [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=1182355393.900282@rumba \
    --to=elwood@agouros.de \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox