all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Non-privileged daemons and offloading
Date: Mon, 20 Jun 2016 14:23:05 +0200	[thread overview]
Message-ID: <87wplk3v86.fsf@gnu.org> (raw)
In-Reply-To: <87y460709u.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 20 Jun 2016 10:05:49 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> Regardless, it remains our best hope to support unprivileged daemons.

Also, I did not explicitly mention it, but I think this unprivileged
user namespace thing should just be one part of the strategy.

In parallel, it’s worth discussing with cluster sysadmins and see if
they can have guix-daemon running on the cluster.  There are good
reasons for them to do that compared to letting each user do their own
thing, and one of them is improved resource usage.

Ricardo outlined the setup he came up with on a cluster here:

  http://elephly.net/posts/2015-04-17-gnu-guix.html

and we have a bunch of arguments in store ;-):

  https://hal.inria.fr/hal-01161771/en

In the end, for a sysadmin, it’s a cost/benefit tradeoff.  In some
situations, providing Guix may mean much less work for cluster admins.

Ludo’.

  reply	other threads:[~2016-06-20 12:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-19 13:07 Non-privileged daemons and offloading Ben Woodcroft
2016-06-20  8:05 ` Ludovic Courtès
2016-06-20 12:23   ` Ludovic Courtès [this message]
2016-06-20 12:44   ` Thompson, David
2016-06-20  9:06 ` Roel Janssen
2016-07-30  4:11   ` Ben Woodcroft

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wplk3v86.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=b.woodcroft@uq.edu.au \
    --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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.