From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: binary installation on Fedora 25
Date: Sat, 28 Jan 2017 13:00:24 +0100
Message-ID: <87fuk375t3.fsf@elephly.net>
References: <CAJ98PDwX13m2KC3tOhC5=J2Kv_yyq0ugXRd1hRv7h_=n8V_m-w@mail.gmail.com>
	<87efzo19x0.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36839)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1cXRgS-0005vv-OV
	for help-guix@gnu.org; Sat, 28 Jan 2017 07:00:45 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1cXRgP-00086u-OC
	for help-guix@gnu.org; Sat, 28 Jan 2017 07:00:44 -0500
Received: from sender163-mail.zoho.com ([74.201.84.163]:21098)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <rekado@elephly.net>) id 1cXRgP-00086B-F9
	for help-guix@gnu.org; Sat, 28 Jan 2017 07:00:41 -0500
In-reply-to: <87efzo19x0.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix/>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix <help-guix@gnu.org>


Marius Bakke <mbakke@fastmail.com> writes:

> Catonano <catonano@gmail.com> writes:
[=E2=80=A6]
>> Several times selinux complained that some process was trying to read so=
me
>> file unduly.
>
> I think SELinux needs to be disabled, since we don't have any policy for
> the Guix daemon at the moment. Can you try that and report back?

After FOSDEM I could take a look at this and see if I can come up with a
simple SELinux policy.  I don=E2=80=99t think it=E2=80=99s good to suggest =
SELinux be
disabled (other than as a workaround).

--=20
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net