❦ 26 août 2016 15:14 CEST, Ian Jackson :
> Otherwise sysvinit users (and advocates) have to have tiresome
> discussions one package at a time - discussions where the maintainer
> inevitably starts repeating the claims that sysvinit is obsolete and
> should be
On Fri, 26 Aug 2016 14:14:25 +0100 Ian Jackson
wrote:
> Sam Hartman writes ("Re: Bug#835507: Please clarify that sysvinit support
> decision is not going to expire"):
> > I don't want to make a blanket statement that it's a bug not to include
> > an init script.
On Fri, 26 Aug 2016 12:55:56 +0100 Ian Jackson
wrote:
> So: would the TC please clarify that the decision that
>
> For the record, the TC expects maintainers to continue to support
> the multiple available init systems in Debian. That includes
>
Sam Hartman writes ("Re: Bug#835507: Please clarify that sysvinit support
decision is not going to expire"):
> [Ian Jackson:]
> > I am running stretch with sysvinit on my laptop. It seems to
> > work for me. I haven't conducted any kind of systematic
> > survey.
>
> That's the rough estimate I
Ian, quick question for you because you might know the answer off the
top of your head. Does running stretch with sysvinit as your init
system work reasonably well, or at least work well enough that there are
a small number of bugs we will likely be able to fix in the stretch time
frame? What I
Sam Hartman writes ("Re: Bug#835507: Please clarify that sysvinit support
decision is not going to expire"):
> Ian, quick question for you because you might know the answer off the
> top of your head. Does running stretch with sysvinit as your init
> system work reasonably well, or at least work
> "Ian" == Ian Jackson writes:
Ian> Sam Hartman writes ("Re: Bug#835507: Please clarify that
Ian> sysvinit support decision is not going to expire"):
>> Ian, quick question for you because you might know the answer off
>> the top of your head.
Package: tech-ctte
There has recently been a thread on debian-devel ("Is missing
SysV-init support a bug?) about the decision by a package maintainer
to drop sysvinit support from their package. The maintainer has said
they are reconsidering, which is good.
But, the discussion on -devel has
On Fri, 2016-08-26 at 12:38 -0400, Sam Hartman wrote:
> "Ansgar" == Ansgar Burchardt writes:
>
> Ansgar> On Fri, 26 Aug 2016 08:50:13 -0400 Sam Hartman wrote:
> >> I think we want to reaffirm that policy section 9.3.2 and
> section
> Ansgar> 9.3.3
> >>
> "Ansgar" == Ansgar Burchardt writes:
Ansgar> On Fri, 26 Aug 2016 08:50:13 -0400 Sam Hartman wrote:
>> I think we want to reaffirm that policy section 9.3.2 and section
Ansgar> 9.3.3
>> represent current policy for init scripts, quoting particularly
>>
> quick question for you because you might know the answer off the top of
> your head. Does running stretch with sysvinit as your init system work
> reasonably well
As for server uses, everything I know about works as good or better as with
systemd (you get to avoid a number of bugs with
On Fri, 26 Aug 2016 08:50:13 -0400 Sam Hartman wrote:
> I think we want to reaffirm that policy section 9.3.2 and section
9.3.3
> represent current policy for init scripts, quoting particularly the
> following text from section 9.3.2:
>
> Packages that include daemons for system services
On Fri, 26 Aug 2016 14:14:25 +0100, Ian Jackson wrote:
> Sam Hartman writes ("Re: Bug#835507: Please clarify that sysvinit support
> decision is not going to expire"):
> > Ian, quick question for you because you might know the answer off the
> > top of your head. Does running stretch with
13 matches
Mail list logo