unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Guix binary tarball
Date: Fri, 15 May 2015 18:46:02 +0200	[thread overview]
Message-ID: <20150515164602.GA13539@debian> (raw)

Hello,

we just set up guix 0.8.2 via the binary tarball on a machine at work, and
experienced a few problems:

- The files all have owner nixbld and group nixbld, whereas on my own machine,
  they are either both root (for /var/guix, /root and /store) or user root,
  group guix-builder (for /gnu/store). As that user and group do not exist
  on the target system, the numerical values 30000 and 30001 are used instead.
  Would it be possible to create the tarball with the correct file owner?
  One would then need to modify the documentation, since one needs to first
  create the guix-builder group and add root to it _before_ unpacking the
  tarball, so that the correct owner will be chosen instead of the numerical
  value.
- The tarball also contains /, /root and /var. When unpacking it, the owner
  and permissions are changed on the system. As a consequence, we could not
  ssh into the machine any more (!). Could these directories be left out of
  the tarball and only their contents be kept in?

Another point, which might simply lead to modifications in the documentation:

- /root/.guix-profile does not need to be accessed by a normal user. I think
  that it is better to do
  # cd /usr/local/bin
  # ln -s /var/guix/profiles/per-user/root/guix-profile/bin/guix
  instead of
  # ln -s /root/.guix-profile/bin/guix
  This unravels one layer of symbolic links, and does not force to change
  the permissions of /root.

Andreas

             reply	other threads:[~2015-05-15 16:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 16:46 Andreas Enge [this message]
2015-05-15 17:14 ` Guix binary tarball Ludovic Courtès
2015-05-15 17:37   ` Andreas Enge
2015-05-15 19:45     ` Taylan Ulrich Bayırlı/Kammer
2015-05-16 18:55       ` Ludovic Courtès
2015-05-16  2:53     ` Mark H Weaver
2015-05-17 21:34       ` Ludovic Courtès
2015-05-16  6:47   ` Andreas Enge
2015-05-16 18:57     ` Ludovic Courtès
2015-05-17 22:15   ` Ludovic Courtès
2015-05-17 22:45     ` Ludovic Courtès
2015-05-18 11:34       ` Andreas Enge
2015-05-18 19:38         ` Ludovic Courtès
2015-05-19 23:03 ` Mark H Weaver
2015-05-20  8:10   ` Andreas Enge
2015-05-20 10:19   ` Ludovic Courtès
2015-05-20 19:12     ` Mark H Weaver
2015-05-21  8:16       ` Ludovic Courtès
2015-06-07 12:39 ` Thomas Schwinge
2015-06-07 13:16   ` /run/current-system (was: Guix binary tarball) Thomas Schwinge
2015-06-07 16:19     ` /run/current-system Ludovic Courtès
2015-06-07 16:14   ` Guix binary tarball Ludovic Courtès
2015-06-08  9:34     ` Alex Kost
2015-06-08 21:33       ` 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=20150515164602.GA13539@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@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.
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).