On Sun 02/Jul/2017 15:13:06 +0200 Christian Seiler wrote:
> (To clarify: I'm not saying that people who don't like systemd
> can't be rational, but I do think that anyone who claims to see
> a conspiracy here is not taking a rational position.)
Admittedly it was somewhat tongue-in-cheek, although
On Sun, Jul 2, 2017 at 8:37 PM, Alessandro Vesely wrote:
> On Sun 02/Jul/2017 12:37:33 +0200 Christian Seiler wrote:
>> On 07/02/2017 11:24 AM, Michael Fothergill wrote:
>>> Could this be exploited to force people to use sysvinit instead of systemd ?
>
> :-)
:-|
>> This bug has nothing to do wit
The Wanderer wrote:
> That project is made up of people, and those people could potentially
> be (in) a conspiracy.
A conspiracy of egomania and selfishness :D
On 07/02/2017 01:37 PM, Alessandro Vesely wrote:
> On Sun 02/Jul/2017 12:37:33 +0200 Christian Seiler wrote:
>> This bug has nothing to do with systemd as the init system, it's in an
>> optional component that's disabled by default on Debian. In principle,
>> I suspect that resolved could also be u
On 2017-07-02 at 08:42, Curt wrote:
> On 2017-07-02, Alessandro Vesely wrote:
>
>> I'd be curious on why tools which don't even require that systemd
>> be PID1 go under the systemd umbrella. Doesn't that contribute to
>> make systemd appear like some kind of conspiracy?
>
> A piece of software
On 2017-07-02, Alessandro Vesely wrote:
>
> I'd be curious on why tools which don't even require that systemd be PID1 go
> under the systemd umbrella. Doesn't that contribute to make systemd appear
> like some kind of conspiracy?
A piece of software cannot be a conspiracy. A conspiracy requires
On Sun 02/Jul/2017 12:37:33 +0200 Christian Seiler wrote:
> On 07/02/2017 11:24 AM, Michael Fothergill wrote:
>> Could this be exploited to force people to use sysvinit instead of systemd ?
:-)
> This bug has nothing to do with systemd as the init system, it's in an
> optional component that's d
On 07/02/2017 11:24 AM, Michael Fothergill wrote:
> Could this be exploited to force people to use sysvinit instead of systemd ?
This bug has nothing to do with systemd as the init system, it's in an
optional component that's disabled by default on Debian. In principle,
I suspect that resolved co
8 matches
Mail list logo
