From: ludo@gnu.org (Ludovic Courtès)
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: How to install guix without root permission
Date: Fri, 06 Jan 2017 16:53:19 +0100 [thread overview]
Message-ID: <87lguokwwg.fsf@gnu.org> (raw)
In-Reply-To: <40b375d5-3f52-5dbe-1c97-140f6d23b1b0@tobias.gr> (Tobias Geerinckx-Rice's message of "Fri, 6 Jan 2017 15:18:00 +0100")
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> On 06/01/17 14:59, rohit yadav wrote:
>> 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.
>
> I do exactly that as regular user on a shared shell server.
Oh, cool!
> It avoids the drawbacks mentioned by Ludo', except for the lack of hard
> build isolation: I just used --disable-chroot to side-step the build
> user group issue. There may be ways around that too.
OTOH, PRoot can presumably provide some level of isolation already,
by simply having /gnu/store visible to the guix-daemon process, and not
/usr/bin etc.
Good to hear that it works for you, I’ll have to give it a try!
Ludo’.
next prev parent reply other threads:[~2017-01-06 15:53 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 [this message]
2017-01-06 15:18 ` Ludovic Courtès
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
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=87lguokwwg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).