On Sat, Nov 16, 2019 at 09:01:45PM -0800, Russ Allbery wrote:
> > I also don't think it is appropriate to consider something overriding a
> > delegate unless it is overiding a specific decision of a delegate.
>
> For the record, it's not possible in this case to override a decision of
> the delega
Here I formally propose following option, withdrawing any previous
versions.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Being able to run Debian systems with init systems other than
systemd continues to be value for the project. Package MUST work
with pid1 != systemd
Ian Jackson writes:
> I hereby formally propose the following amendent (for my reference,
> 42471fd). Replace the entire text, with the text below.
>
> -8<-
>
> Title: Support non-systemd systems, without blocking progress
>
> PRINCIPLES
>
> 1. We wish to continue to support multiple init sys
Hi Brian
On Fri, Nov 15, 2019 at 01:10:58AM -0500, Brian Gupta wrote:
> Do you think it's ok in any case to remove init scripts. Let's say an
> upstream stops maintaining init scripts,
I would like to know if this is a real world problem. Please provide an
example of a package where the init scr
Hi,
On 2019/11/16 20:18, Ian Jackson wrote:> I hereby formally propose the
following amendent (for my reference,
> 42471fd). Replace the entire text, with the text below.
I too second the below quoted amendment.
>
> -8<-
>
> Title: Support non-systemd systems, without blocking progress
>
> P
Hi,
On 2019/11/17 18:05, Dmitry Bogatov wrote:
>
> Here I formally propose following option, withdrawing any previous
> versions.
>
> Being able to run Debian systems with init systems other than
> systemd continues to be value for the project. Package MUST work
> with pid1 != sy
[2019-11-17 19:56] Kyle Robbertze
> > Here I formally propose following option, withdrawing any previous
> > versions.
> >
> > Being able to run Debian systems with init systems other than
> > systemd continues to be value for the project. Package MUST work
> > with pid1 != systemd,
The debate on systemd often turns into systemd vs. sysvinit because sysvinit is
the working alternative right now. Unfortunately, this is a poor way
to frame the
debate. The reality is sytemd unit files are a really good idea, but systemd's
hardware detection leaves much to be desired.
You're goin
Joshua Hudson writes:
> The debate on systemd often turns into systemd vs. sysvinit because
> sysvinit is the working alternative right now. Unfortunately, this is a
> poor way to frame the debate. The reality is sytemd unit files are a
> really good idea, but systemd's hardware detection leaves
On 11/15/19 6:49 PM, Russ Allbery wrote:
> Ian Jackson writes:
>
>> Here is my proposal. It is unfortunately quite long. The reason is
>> that I am trying to address the dysfuncdtional patterns I have seen over
>> the past few years, and give specific remedies.
>
> After sleeping on this, I am
On 11/15/19 12:58 PM, Sam Hartman wrote:
>> "Ian" == Ian Jackson writes:
>
> Ian> Sam Hartman writes ("Proposal: General Resolution on Init
> Ian> Systems and systemd Facilities"):
> >> Timeline:
>
> Ian> Please can we have more time.
>
> If you're worried about still finali
11 matches
Mail list logo
