unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ni* <niasterisk@grrlz.net>
To: help-guix@gnu.org
Subject: Guix with Debian GNU/Linux
Date: Wed, 30 Dec 2015 14:45:03 +0100	[thread overview]
Message-ID: <871ta4m4o0.fsf@grrlz.net> (raw)

I will soon setup a number of new servers with Debian GNU/Linux.
I decided to run them with GNU/Guix for packages and strip down
the image I get installed as much as possible.
So I have some questions for using Debian Jessie with GNU/Guix:

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?

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)

What are things I should look for and be careful about? What can be
removed from the hostsystem, what needs to stay?
Are guix updates handled the same way as they are done in GuixSD
(guix pull ; guix package -u)?

I will the manual before I setup the systems, but I thought asking some
questions before would be better. I am sure some of the questions I have
are answered in the manual.

-- 
ng/Ni*
http://libertad.pw:8080
Email is public. Talk to me in private:
https://psyced.org:34443/~niasterisk
privacy respecting, secure communication:
BM-2cSj8qEigE3CMaLU3CwPZf7T3LvzvnttsC
(bitmessage)

             reply	other threads:[~2015-12-30 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 13:45 Ni* [this message]
2015-12-30 17:47 ` Guix with Debian GNU/Linux Ludovic Courtès
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=871ta4m4o0.fsf@grrlz.net \
    --to=niasterisk@grrlz.net \
    --cc=help-guix@gnu.org \
    /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).