>Also, if one really, really, really needs a systemd burdened software,
>he could always run it in a Docker container.
Hey, Steve! Good to hear from you!
Now that is a very good point. Unfortunately, running systemd inside of
Docker container requires a privileged container and does
On Thu, 16 Apr 2015 12:17:43 -0700
Go Linux wrote:
>
>
> On Thu, 4/16/15, Anto wrote:
>
> Subject: Re: [Dng] Purpose of systemd-shim
> To: dng@lists.dyne.org
> Date: Thursday, April 16, 2015, 1:05 PM
>
>
> >
On Thu, 4/16/15, Anto wrote:
Subject: Re: [Dng] Purpose of systemd-shim
To: dng@lists.dyne.org
Date: Thursday, April 16, 2015, 1:05 PM
> This is my personal opinion and I don't know what will happen to Devuan
> even in the next 6 m
On 16/04/15 03:51, T.J. Duchene wrote:
Heyo. Wanted to see how things are going.
The main purpose of a systemd-shim is to allow code that depends on
systemd to be compiled and execute cleanly, without having to actually
introduce a binary dependency on systemd. Whether or not that is
actuall
On Thu, Apr 16, 2015 at 2:51 AM, T.J. Duchene wrote:
> From a user standpoint, it lets them use software that they might not
> otherwise have on Devuan.
Yet.
Right?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/l
On 2015-04-15 19:01, Hendrik Boom wrote:
> On Wed, Apr 15, 2015 at 06:39:29PM +0200, Franco Lanza wrote:
> > On Wed, Apr 15, 2015 at 01:22:28PM +0200, Paul van der Vlis wrote:
> > >
> > > systemd-shim is for when you *don't* want systemd.
> >
> > Yes, but cause of you have things that depend
On 15/04/15 21:01, Hendrik Boom wrote:
On Wed, Apr 15, 2015 at 06:39:29PM +0200, Franco Lanza wrote:
On Wed, Apr 15, 2015 at 01:22:28PM +0200, Paul van der Vlis wrote:
systemd-shim is for when you *don't* want systemd.
Yes, but cause of you have things that depend on components of systemd.
We
On Wed, Apr 15, 2015 at 06:39:29PM +0200, Franco Lanza wrote:
> On Wed, Apr 15, 2015 at 01:22:28PM +0200, Paul van der Vlis wrote:
> >
> > systemd-shim is for when you *don't* want systemd.
>
> Yes, but cause of you have things that depend on components of systemd.
> We don't want systemd nor any
