On Tue, 8 May 2018, to...@tuxteam.de wrote:
On Tue, May 08, 2018 at 02:23:57AM +0300, Abdullah Ramazanoğlu wrote:
Is anyone working on a mechanism to allow for install-time selection
of a desired init? I brought this up a few times since systemd came
to Debian, but I've never heard anything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 08, 2018 at 02:23:57AM +0300, Abdullah Ramazanoğlu wrote:
[...]
> >> Is anyone working on a mechanism to allow for install-time selection
> >> of a desired init? I brought this up a few times since systemd came
> >> to Debian, but I've
On Mon, 7 May 2018 12:40:13 -0700 Patrick Bartek said:
> On Mon, 7 May 2018 01:25:15 + (UTC) David Griffith
> wrote:
>> Is anyone working on a mechanism to allow for install-time selection
>> of a desired init? I brought this up a few times since systemd came
>> to Debian,
On Mon, 7 May 2018 01:25:15 + (UTC) David Griffith
wrote:
> On Sun, 6 May 2018, Patrick Bartek wrote:
>
> > On Sun, 6 May 2018 02:44:16 + (UTC) David Griffith
> > wrote:
> >
> >> Have any advances been made in figuring out just how to remove
> >>
David Griffith writes:
> On Sun, 6 May 2018, The Wanderer wrote:
>> On 2018-05-06 at 21:25, David Griffith wrote:
>>
>>> What's the point of allowing libsystemd0 to exist when systemd has
>>> been purged?
>>
>> So that programs which interface with systemd can detect whether or not
>> systemd is
On Sun, 6 May 2018, The Wanderer wrote:
On 2018-05-06 at 21:25, David Griffith wrote:
What's the point of allowing libsystemd0 to exist when systemd has
been purged?
So that programs which interface with systemd can detect whether or not
systemd is present, and fall back to alternate code
On 2018-05-06 at 21:25, David Griffith wrote:
> What's the point of allowing libsystemd0 to exist when systemd has
> been purged?
So that programs which interface with systemd can detect whether or not
systemd is present, and fall back to alternate code paths when it's not.
As I understand
On Sun, 6 May 2018, Patrick Bartek wrote:
On Sun, 6 May 2018 02:44:16 + (UTC) David Griffith
wrote:
Have any advances been made in figuring out just how to remove
libsystemd0 from a Debian 9 machine that's running sysvinit? The
ongoing presence of libsystemd0 has caused
On Sun, 6 May 2018 02:44:16 + (UTC) David Griffith
wrote:
>
> Have any advances been made in figuring out just how to remove
> libsystemd0 from a Debian 9 machine that's running sysvinit? The
> ongoing presence of libsystemd0 has caused slowly-progressing trouble
> with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, May 06, 2018 at 02:44:16AM +, David Griffith wrote:
>
> Have any advances been made in figuring out just how to remove
> libsystemd0 from a Debian 9 machine that's running sysvinit? The
> ongoing presence of libsystemd0 has caused
Have any advances been made in figuring out just how to remove libsystemd0
from a Debian 9 machine that's running sysvinit? The ongoing presence of
libsystemd0 has caused slowly-progressing trouble with several machines of
mine culminating in complete failure a couple days ago. Initially I
11 matches
Mail list logo