control: tags -1 +wontfix
[2019-12-05 10:32] Thomas Goirand
> Source: sysvinit
> Severity: normal
>
> Dear sysvinit maintainers,
>
> OpenRC is actively maintained upstream, and is a full replacement of sysv-rc,
> including many improvements.
>
> Currently, packages are stuck with long,
> Thomas Goirand writes:
>
> So, my proposal is to get rid of sysv-rc provided by sysvinit, in the
favor of
> OpenRC, so that developers can start replacing their init scripts by
superior
> runscripts.
Please don't: runit uses sysvinit scripts as a fallback for a missing
runscript (with
On 12/6/19 2:30 AM, Benda Xu wrote:
> Hi Thomas,
>
> Thomas Goirand writes:
>
>>> The last time I looked (years ago), there were features in sysvinit
>>> which weren't in OpenRC (yet). IIRC not having concurrent execution of
>>> boot scripts was one of the missing features and the reason for
Hi Thomas,
Thomas Goirand writes:
>> The last time I looked (years ago), there were features in sysvinit
>> which weren't in OpenRC (yet). IIRC not having concurrent execution of
>> boot scripts was one of the missing features and the reason for e.g.
>> our derivative distribution GRML to not
On Thu, 5 Dec 2019, Thomas Goirand wrote:
> Thorsten Glaser
> > Dropping sysvinit as it works and as admins know... no.
> > Absolutely NOT.
>
> Thorsten, do you have any point of argumentation besides "it works and
> we know it"? That's IMO a bit light...
I don’t want to learn a new init
Hi Thomas,
Thomas Goirand wrote:
> > Maybe packages can ship them somewhere else than default, and openrc
> > uses dpkg-divert to get them into the expected path if and only if
> > openrc is installed.
>
> Files in /etc/init.d are CONFFILE files. I don't think dpkg-divert works
> with CONFFILE
Hi Alex,
Axel Beckert
> Thomas Goirand wrote:
> > OpenRC is actively maintained upstream,
>
> Sysvinit is AFAIK maintained upstream again since a year ago or so. So
> this is no reason to get rid of sysvinit. Note all the new upstream
> releases, Dmitry has uploaded in the past year:
>
On Thu, 5 Dec 2019, Thomas Goirand wrote:
> Your thoughts?
No.
Supporting it as an alternative, granted, not even worth discussing.
Dropping sysvinit as it works and as admins know… no. Absolutely NOT.
bye,
//mirabilos
--
Yes, I hate users and I want them to suffer.
-- Marco d'Itri
Hi Thomas,
Thomas Goirand writes:
> OpenRC is actively maintained upstream, and is a full replacement of
> sysv-rc, including many improvements.
>
> Currently, packages are stuck with long, non-declarative sysv-rc
> scripts, and cannot switch to superior runscripts, interpreted by
>
Hi,
Thomas Goirand wrote:
> OpenRC is actively maintained upstream,
Sysvinit is AFAIK maintained upstream again since a year ago or so. So
this is no reason to get rid of sysvinit. Note all the new upstream
releases, Dmitry has uploaded in the past year:
Source: sysvinit
Severity: normal
Dear sysvinit maintainers,
OpenRC is actively maintained upstream, and is a full replacement of sysv-rc,
including many improvements.
Currently, packages are stuck with long, non-declarative sysv-rc scripts, and
cannot switch to superior runscripts, interpreted
11 matches
Mail list logo