unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Sébastien Lerique" <sl@eauchat.org>
To: guix-science@gnu.org
Subject: Introducing Guix to HPC at my institution
Date: Mon, 15 Mar 2021 12:12:30 +0900	[thread overview]
Message-ID: <878s6pds9t.fsf@eauchat.org> (raw)

Hi all,

I'm interested in introducing Guix to the HPC team at my 
institution. There's quite some content on the Guix-HPC blog [0], 
but I was wondering if people here have stories about how such 
conversations went for them, which arguments worked best, which 
didn't.

As a first step I would like to discuss with the sysadmins if they 
would consider activating user namespaces so users can play 
around. Aside from [1] and [2], are there any updated discussions 
about this topic, e.g. why to do it or why not?

Best,
Sébastien


[0] https://hpc.guix.info/blog/
[1] 
https://hpc.guix.info/blog/2017/10/using-guix-without-being-root/
[2] 
https://hpc.guix.info/blog/2017/09/reproducibility-and-root-privileges/


             reply	other threads:[~2021-03-15  5:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  3:12 Sébastien Lerique [this message]
2021-03-15 13:47 ` Introducing Guix to HPC at my institution zimoun
2021-03-16  1:54   ` Sébastien Lerique
2021-03-16  8:06     ` zimoun
2021-03-16  9:05     ` Ludovic Courtès
2021-03-18  2:26       ` Sébastien Lerique
2021-03-26  8:22         ` Sébastien Lerique
2021-03-29 12:03           ` Ludovic Courtès
2021-03-30  1:54             ` Sébastien Lerique
2021-03-30  7:21               ` Ludovic Courtès
2021-03-31  5:23                 ` Sébastien Lerique
2021-04-01  8:35                   ` Ludovic Courtès
2021-04-01 14:34                     ` Sébastien Lerique
2021-04-10 20:43                       ` Ludovic Courtès
2021-04-12  1:21                         ` Sébastien Lerique
2021-04-12 12:43                           ` 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=878s6pds9t.fsf@eauchat.org \
    --to=sl@eauchat.org \
    --cc=guix-science@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).