all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: rohit yadav <rohityadav@utexas.edu>
Cc: help-guix@gnu.org
Subject: Re: How to install guix without root permission
Date: Fri, 06 Jan 2017 16:18:09 +0100	[thread overview]
Message-ID: <87r34gkyj2.fsf@gnu.org> (raw)
In-Reply-To: <CAGKZdmacg1gvKoWwBnCJ1v-2bDBzHKGCpBBRDXJJ9ZCsWA2ZFA@mail.gmail.com> (rohit yadav's message of "Fri, 6 Jan 2017 07:59:44 -0600")

rohit yadav <rohityadav@utexas.edu> skribis:

> ​Thanks for the reply. ​The proot (https://proot-me.github.io/) project
> allows you to map $HOME/gnu/store to /gnu/store etc. However, where I am
> struggling is the guixbuild users and group creation, and running guix
> daemon.

Yes, though PRoot relies on syscall interception using ptrace(2), which
is inefficient (which may or may not be a problem, depending on the
application).

> I am using kernel 4+, which supports namespaces.

Yes, but some distributions compile it out or turn it off by default.
See
<http://git.savannah.gnu.org/cgit/guix.git/tree/guix/scripts/environment.scm#n517>,
for a way to check whether user namespaces are enabled.

> This reminds if there is any effort to provide a lxc container for
> guixSD.

Not that I know of, but I don’t think it would help the non-root use
case.

Ludo’.

  parent reply	other threads:[~2017-01-06 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  0:59 How to install guix without root permission rohit yadav
2017-01-06 13:49 ` Ludovic Courtès
2017-01-06 13:59   ` rohit yadav
2017-01-06 14:18     ` Tobias Geerinckx-Rice
2017-01-06 15:53       ` Ludovic Courtès
2017-01-06 15:18     ` Ludovic Courtès [this message]
2017-01-06 23:26       ` rohit yadav
2017-01-07 21:06         ` 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

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

  git send-email \
    --in-reply-to=87r34gkyj2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=rohityadav@utexas.edu \
    /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.