On Sunday, August 24, 2014 9:40:01 AM UTC+2, Joe wrote:
> On Sat, 23 Aug 2014 14:24:59 -0700 (PDT)
>
> Alexandre Ferrieux wrote:
>
> > systemd allows to continue using sysvinit scripts, service per
> > service. It just doesn't preserve the integrity at the system level.
>
> On the whole, it does
On Sat, Aug 23, 2014 at 5:24 PM, Alexandre Ferrieux
wrote:
> On Saturday, August 23, 2014 3:00:02 PM UTC+2, Brian wrote:
>> On Fri 22 Aug 2014 at 17:20:03 -0700, Alexandre Ferrieux wrote:
>>> I have a Jessie-based system, which up to the last upgrade used
>>> sysvinit of course, and where I had
On Sat, 23 Aug 2014 14:24:59 -0700 (PDT)
Alexandre Ferrieux wrote:
> Agreed,
> systemd allows to continue using sysvinit scripts, service per
> service. It just doesn't preserve the integrity at the system level.
On the whole, it does. The only real show-stopper I've seen mentioned
so far was t
On Saturday, August 23, 2014 3:00:02 PM UTC+2, Brian wrote:
> On Fri 22 Aug 2014 at 17:20:03 -0700, Alexandre Ferrieux wrote:
>
> > I have a Jessie-based system, which up to the last upgrade used
> > sysvinit of course, and where I had added sysv-rc-conf, and was
> > happily juggling with a few ru
On Fri 22 Aug 2014 at 17:20:03 -0700, Alexandre Ferrieux wrote:
> I have a Jessie-based system, which up to the last upgrade used
> sysvinit of course, and where I had added sysv-rc-conf, and was
> happily juggling with a few runlevels.
>
> But after an upgrade (still in Jessie), systemd rules. N
Hello,
I have a Jessie-based system, which up to the last upgrade used sysvinit of
course, and where I had added sysv-rc-conf, and was happily juggling with a few
runlevels.
But after an upgrade (still in Jessie), systemd rules. No problem about this,
but what degree of compatibility should I
6 matches
Mail list logo
