unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ni* <niasterisk@grrlz.net>
Cc: help-guix@gnu.org
Subject: Re: Guix with Debian GNU/Linux
Date: Wed, 30 Dec 2015 18:47:14 +0100	[thread overview]
Message-ID: <87bn97q15p.fsf@gnu.org> (raw)
In-Reply-To: <871ta4m4o0.fsf@grrlz.net> (Ni's message of "Wed, 30 Dec 2015 14:45:03 +0100")

Ni* <niasterisk@grrlz.net> skribis:

> From using GuixSD I know that as little files as possible should be
> created in /etc. When using Guix alone, is this still the recommended
> way of doing things?

Most of the time, you can choose where to store config files, in /etc or
elsewhere.

> What I need to know for a server environment is, if I install tor and
> serve non-exit tor relays, will the config be read from the location I
> am used to (/etc/tor/) or does it differ? (same about httpd/nginx, etc)

Most programs allow you to choose which configuration file to use.  For
instance, one can run:

  tor -f /path/to/torrc

and Tor will pick its config file from there.  I think the same is true
of nginx and httpd.

> What are things I should look for and be careful about? What can be
> removed from the hostsystem, what needs to stay?

Compared to GuixSD, a couple of things need tweaking to work smoothly;
see <https://www.gnu.org/software/guix/manual/html_node/Application-Setup.html>.

As to what to keep in the host distro, it’s up to you!

In some cases, you’ll have to make a binary choice; for instance, if you
use Guile from Guix, you’ll have to use Guile packages (say, Guile-SSH,
Guile-JSON, etc.) from Guix as well since otherwise they would end up
loading different variants of libguile.so and libc.so.

> Are guix updates handled the same way as they are done in GuixSD
> (guix pull ; guix package -u)?

Yes.

Out of curiosity, what are the technical reasons that led you to prefer
Guix-over-Debian rather than GuixSD, since you tried GuixSD already?

Thanks,
Ludo’.

  reply	other threads:[~2015-12-30 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 13:45 Guix with Debian GNU/Linux Ni*
2015-12-30 17:47 ` Ludovic Courtès [this message]
2015-12-30 22:21   ` Ni*
2015-12-31  1:12     ` Leo Famulari
2016-01-02  0:10       ` Ni*
2016-01-02  1:10         ` Leo Famulari

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=87bn97q15p.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=niasterisk@grrlz.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).