From: Ricardo Wurmus <rekado@elephly.net>
To: "Sébastien Pierre" <sebastien.pierre@nzx.com>
Cc: help-guix@gnu.org
Subject: Re: Install and reinstall issues on Fedora 34
Date: Wed, 30 Jun 2021 23:01:52 +0200 [thread overview]
Message-ID: <87k0mbukvz.fsf@elephly.net> (raw)
In-Reply-To: <CANBUJkyPfOH5Ri-nrWxCTcF3AL0UOwgSgUkej_SpiT3iQS2MUw@mail.gmail.com>
Hi,
Sébastien Pierre <sebastien.pierre@nzx.com> writes:
> I am evaluating Guix and am running into some issues getting it
> to work
> under Fedora 34 Workstation. I followed the binary install
> instructions
> <https://guix.gnu.org/manual/en/html_node/Binary-Installation.html>,
> running the install script from an interactive root shell. All
> went well, I
> rebooted the VM, but then guix-daemon failed to start:
I suggest running the guix-daemon command manually first to
diagnose this.
> But the same Permission Denied/Failed to locate issue remains. I
> know that
> Fedora uses SELinux which sometimes causes some problems, but
> I'm not sure
> about how to resolve that.
There are really just two ways: either 1) disable SELinux (or set
it to permissive mode) or 2) install/debug/reinstall the SELinux
daemon policy that is included with Guix.
The daemon policy is *not* installed with the binary installation
method because it is known to be incomplete. You would need to
get a copy of the Guix sources and configure it. The file you
want is called “etc/guix-daemon.cil”. To debug it you would need
to install it, set SELinux to permissive mode, run the daemon, and
then check the audit log for errors.
If you just want to start playing with Guix *right now* I suggest
temporarily disabling SELinux.
--
Ricardo
prev parent reply other threads:[~2021-06-30 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 22:57 Install and reinstall issues on Fedora 34 Sébastien Pierre
2021-06-30 15:39 ` Joshua Branson
2021-06-30 21:01 ` 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=87k0mbukvz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=sebastien.pierre@nzx.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).