unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Installer script on Fedora doesn't work properly
Date: Wed, 01 Jul 2020 00:30:40 +0200	[thread overview]
Message-ID: <87h7usmbjj.fsf@elephly.net> (raw)
In-Reply-To: <20200630232209.1bb69ead@interia.pl>


Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl> writes:

>> This means the daemon isn’t running.
>> 
>> If you use SELinux in enforcing mode then the daemon is probably
>> prevented from starting.
> I'm not aware of this - I just picked all default settings, not that
> the choice was big.

It’s not Guix, it’s Fedora.  Fedora ships with SELinux enabled by
default, which means that all software needs to have a policy that
declares in what context it runs and what other contexts it can access.

>> Sure.  We have a draft SELinux policy for systems like yours, but it
>> is probably no longer current as Fedora’s SELinux policy is not
>> frozen in time.  I encourage you to try it and help debug it to
>> adjust it for current versions of Fedora.
> That's my first day running Fedora, but if someone gives me right
> directions, I can help.

The first thing to do is to install the guix-daemon.cil file as
explained in the manual.  That file is part of the Guix source
repository.

Then as you start guix-daemon you need to look at
/var/log/audit/audit.log (or similar) to see why SELinux blocked the
daemon from running.

-- 
Ricardo


      reply	other threads:[~2020-06-30 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 22:04 Installer script on Fedora doesn't work properly Jan Wielkiewicz
2020-06-30 10:55 ` jbranso
2020-06-30 12:07 ` Ricardo Wurmus
2020-06-30 21:27   ` Jan Wielkiewicz
2020-06-30 22:30     ` Ricardo Wurmus [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7usmbjj.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).