From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Update on GuixSD containers
Date: Fri, 12 Jun 2015 21:41:34 -0400 [thread overview]
Message-ID: <CAJ=RwfbZMYjH7+2iHYpNoC5+vEJCr-k0LxG8cauo4ituMH3j5w@mail.gmail.com> (raw)
In-Reply-To: <87381xklk6.fsf@gnu.org>
On Fri, Jun 12, 2015 at 11:12 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> "Thompson, David" <dthompson2@worcester.edu> skribis:
>
>> Yeah, our daemon would do the same thing. We could maybe even have a
>> little Guile library that allows one to evaluate arbitrary scheme code
>> from within the container. :)
>
> Actually, something quite easily feasible would be this:
>
> (eval-in-container #~(system* #$evil-program
> #$(local-file "important-data.txt"))
> #:networking? #f)
>
> ... where the container’s store would be populated with just
> EVIL-PROGRAM and the local file.
>
> Food for thought...
Ooooh yeah! That would be cool. Though I think we should still spawn
a dmd process as PID 1 to deal with reaping zombie processes. We
could generate a single service that runs the gexp script. How does
that sound?
Thanks for this good idea!
- Dave
next prev parent reply other threads:[~2015-06-13 1:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 15:20 Update on GuixSD containers Thompson, David
2015-06-09 21:28 ` Ludovic Courtès
2015-06-11 14:51 ` Thompson, David
2015-06-12 15:08 ` Ludovic Courtès
2015-06-13 3:41 ` Thompson, David
2018-07-24 22:22 ` Christopher Lemmer Webber
2015-06-12 15:12 ` Ludovic Courtès
2015-06-13 1:41 ` Thompson, David [this message]
2015-06-13 13:06 ` Ludovic Courtès
2015-06-13 13:14 ` Thompson, David
2015-06-13 20:19 ` Ludovic Courtès
2015-06-16 16:39 ` Thompson, David
2015-06-19 12:08 ` Ludovic Courtès
2015-06-19 12:29 ` Thompson, David
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='CAJ=RwfbZMYjH7+2iHYpNoC5+vEJCr-k0LxG8cauo4ituMH3j5w@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
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.