From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Clément Lassieur" <clement@lassieur.org>,
"Ricardo Wurmus" <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Updating guix for root
Date: Thu, 30 Aug 2018 17:02:42 +0200 [thread overview]
Message-ID: <m1zhx3hp7x.fsf@fastmail.net> (raw)
In-Reply-To: <87tvne784m.fsf@lassieur.org>
Hi Clément and Ricardo,
Thanks for your replies!
I conclude from them that there is no clear recommendation yet for
dealing with this situation, so for the meantime I applied
>> 1) update /etc/systemd/system/guix-daemon.service
>> to point to the current daemon? If so, is
>> /root/.config/guix/current/bin/guix-daemon
>> the right (stable) path to use?
I prefer to point to /root rather then to my $HOME which is less
reliable for reasons completely unrelated to Guix (it's on a zfs volume
shared with macOS).
So far (i.e. for about a day) this seems to work fine!
Thanks again,
Konrad.]
next prev parent reply other threads:[~2018-08-30 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 12:47 Updating guix for root Konrad Hinsen
2018-08-28 16:45 ` Clément Lassieur
2018-08-30 15:02 ` Konrad Hinsen [this message]
2018-08-28 19:25 ` Ricardo Wurmus
2018-09-01 14:32 ` Ludovic Courtès
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=m1zhx3hp7x.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=clement@lassieur.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).