From: ludovic.courtes@inria.fr (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Generating wrappers for execution in non-root non-Guix contexts
Date: Thu, 26 Apr 2018 16:58:59 +0200 [thread overview]
Message-ID: <87po2m10b0.fsf@inria.fr> (raw)
In-Reply-To: <87fu3it7cm.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 26 Apr 2018 15:39:21 +0200")
Hey!
Ricardo Wurmus <rekado@elephly.net> skribis:
>> We could also have wrappers fall back to PRoot when unshare(2) fails.
>
> Good idea. Could we use ptrace directly and optimize it for the case of
> “/gnu/store” paths? I’m just guessing that PRoot may incur a higher
> performance penalty because it’s so generic compared to a compile-time
> deterministic use of ptrace – after all, we know all /gnu/store
> locations in advance.
IWBN, but that’s a project in its own. ptrace(2) requires knowledge
about the architecture’s ABI so that you know what registers to look at
when a syscall happens, and so on. So for now it’ll have to be PRoot.
I’ll try to come up with a patch set without PRoot support to begin
with.
Thanks for your feedback,
Ludo’.
next prev parent reply other threads:[~2018-04-26 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 9:14 Generating wrappers for execution in non-root non-Guix contexts Ludovic Courtès
2018-04-25 9:19 ` Pierre Neidhardt
2018-04-25 12:44 ` Ludovic Courtès
2018-04-26 13:39 ` Ricardo Wurmus
2018-04-26 14:58 ` Ludovic Courtès [this message]
2018-04-27 3:21 ` Chris Marusich
2018-04-27 16:38 ` Ludovic Courtès
2018-05-03 20:51 ` 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=87po2m10b0.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).