On Wed, 2017-03-01 at 21:11 +1000, Michi Henning wrote:
> >
> >
> > That's not true. When a command or daemon in a strict mode snap gets
> > executed, it runs in a different mount namespace where the file system
> > root is the contents of the "core" snap. You can verify this by
> > executing t
>
> That's not true. When a command or daemon in a strict mode snap gets
> executed, it runs in a different mount namespace where the file system
> root is the contents of the "core" snap. You can verify this by
> executing the following:
>
>snap run --shell command_name
>
> .. and use tha
On 1 March 2017 at 07:13, Michi Henning wrote:
>
>> Upon further thinking, I believe that I did not have to use a fresh
>> LXD container, because the "strict" confinement would preclude anyway
>> the snap from using any of my desktop's existing system libraries.
>> Isn't that indeed the case?
>
>
> Upon further thinking, I believe that I did not have to use a fresh
> LXD container, because the "strict" confinement would preclude anyway
> the snap from using any of my desktop's existing system libraries.
> Isn't that indeed the case?
I don’ think so. System libraries are visible even with
Hi All,
Here is a tutorial on how to snap "timg", an image viewer for your
terminal emulator (!?!),
https://blog.simos.info/how-to-create-a-snap-for-timg-with-snapcraft-on-ubuntu/
It is another introductory tutorial that
1. describes an interesting utility (image view for text)
2. deals with a re
