From: "Ludovic Courtès" <ludo@gnu.org>
To: Eric Bavier <ericbavier@centurylink.net>
Cc: guix-devel@gnu.org, Joshua Branson <jbranso@dismail.de>
Subject: Re: Anyone working on packaging Firejail?
Date: Fri, 21 Dec 2018 21:56:58 +0100 [thread overview]
Message-ID: <87a7kymwdh.fsf@gnu.org> (raw)
In-Reply-To: <20181221093922.174232e0@centurylink.net> (Eric Bavier's message of "Fri, 21 Dec 2018 09:39:22 -0600")
Hi Eric,
Eric Bavier <ericbavier@centurylink.net> skribis:
> On Thu, 20 Dec 2018 11:19:07 -0500
[...]
>> > Run icecat, a browser, in a container with
>> >
>> > guix environment --container --network --share=/tmp/.X11-unix
>> > --ad-hoc icecat
>> > export DISPLAY=":0.0"
>> > icecat
>>
>> Is there a way to do this automatically? ie: you don't have to type
>> guix environment --container .... icecat? You just type "icecat?"
>
> That is the major advantage Firejail has over 'guix environment
> --container' currently. It contains a large collection of "profiles"
> for different applications, specifying how exactly to jail them so that
> they can still function.
We also discussed “guix run icecat” as a simpler option:
https://lists.gnu.org/archive/html/help-guix/2018-01/msg00108.html
‘guix run’ can guess parts of the profile, like whether the application
needs X11 or Fontconfig stuff, just by looking at the references of the
application. That said, I’m curious to see what the Firejail profiles
look like and to what extent we’d need to manually annotate packages if
we were to provide similar functionality.
Firejail looks nice!
Ludo’.
next prev parent reply other threads:[~2018-12-21 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 5:50 Anyone working on packaging Firejail? swedebugia
2018-12-20 7:53 ` Pierre Neidhardt
2018-12-20 12:17 ` swedebugia
2018-12-20 12:28 ` swedebugia
2018-12-20 16:19 ` Joshua Branson
2018-12-21 15:39 ` Eric Bavier
2018-12-21 20:55 ` Ludovic Courtès
2018-12-21 20:56 ` Ludovic Courtès
2018-12-21 20:56 ` Ludovic Courtès
2018-12-21 20:56 ` Ludovic Courtès [this message]
2018-12-21 20:58 ` 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=87a7kymwdh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ericbavier@centurylink.net \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.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 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.