unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Florian Thevissen <mail@florian-thevissen.de>
Cc: bug-Guix@gnu.org
Subject: bug#34494: proot-based non-root setup: refusing to run with elevated privileges (UID 0)
Date: Wed, 06 Mar 2019 17:00:34 +0100	[thread overview]
Message-ID: <87d0n4f0wt.fsf@gnu.org> (raw)
In-Reply-To: <3ecb593e-49d1-e728-4a48-d4eaf9a675d2@florian-thevissen.de> (Florian Thevissen's message of "Tue, 5 Mar 2019 19:57:42 +0100")

Hi Florian,

Florian Thevissen <mail@florian-thevissen.de> skribis:

> Hi Ludovic,
>
>    Not really answering your question, but would user namespaces be an
>    option for you? If so,
>    <https://lists.gnu.org/archive/html/guix-devel/2018-05/msg00139.html>
>    might be a simpler option.
>
> Thank you for the suggestion, this does look interesting.
>
> However, the original use-case of using guix in a non-root scenario is
> no longer relevant to me: I was convincing enough to get guix
> root-installed on all relevant machines on which I do not have root
> access. So I can enjoy guix properly, now.

Well, congrats.  :-)

Note that <https://guix-hpc.bordeaux.inria.fr/blog> has some thoughts on
non-root usage that may be of interest to you.

> However, I could very well imagine guix to be used on a per-user
> basis, acting on some sub-directory of $HOME. Afterall, many (most?)
> desktop-systems are used by a single user - or so I would argue…

I agree that non-root usage would be useful; it’s just that the kernel
Linux doesn’t make it easy, unless user namespaces are enabled…

Thanks,
Ludo’.

      reply	other threads:[~2019-03-06 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 20:39 bug#34494: proot-based non-root setup: refusing to run with elevated privileges (UID 0) Florian Thevissen
2019-02-16  6:34 ` Pjotr Prins
2019-02-16  9:04   ` Florian Thevissen
     [not found]     ` <20190216091747.eb6g7znptifbqqbt@thebird.nl>
2019-02-16 10:07       ` Florian Thevissen
2019-03-04 21:45 ` Ludovic Courtès
2019-03-05 18:57   ` Florian Thevissen
2019-03-06 16:00     ` Ludovic Courtès [this message]

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=87d0n4f0wt.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-Guix@gnu.org \
    --cc=mail@florian-thevissen.de \
    /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).