On Mon, 2 Dec 2019 10:13:01 +0100
Edward Bartolo via Dng wrote:
> Dear All,
>
> Inits need to understand unit files, give them that functionality.
> That is far more efficient compared to what you are doing.
>
> Pseudo Code:
> 1) check for the presence of a unit file
> 2) if it exists
> a)
On Tue, 3 Dec 2019 09:02:14 +0100
Denis Roio wrote:
> On Sat, 30 Nov 2019, Hendrik Boom wrote:
>
> > On Fri, Nov 29, 2019 at 07:21:54PM +0100, Massimo Coppola wrote:
> >
> > >
> > > If (assuming that) we are going to lose the source of init scripts
> > > upstream, then it's the only way
On Tue, 3 Dec 2019 23:04:56 +
s@po wrote:
>
> I believe you are talking about Situation 1)( Give SysVInit the
> Knowledge about SystemD unitFiles.. )?
I thought this was settled law. Debian has sysvinit scripts, dropped
ones can be gotten from Wheezy, and in other cases there exists a
Hello all,
>Date: Mon, 2 Dec 2019 10:13:01 +0100
>From: Edward Bartolo via Dng
>Dear All,
>
>Inits need to understand unit files, give them that functionality.
>That is far more efficient compared to what you are doing.
>
>Pseudo Code:
>1) check for the presence of a unit file
>2) if it exists
On 12/3/19 10:02 AM, Denis Roio wrote:
> My opinion however is this: maintaining a *unique package* of version
> controlled init scripts in Devuan is much, much easier than
> maintaining a sysvinit script in each different package, forking it.
>
> I'm not sure about pressing counter-arguments
On Tue, Dec 03, 2019 at 08:58:10AM +0100, Denis Roio wrote:
> I wholeheartedly agree with all your reasoning, quoted below. I don't
> think that converting automatically at init or at package install is a
> good idea: we need to keep this process under scrutiny by maintainers,
> hoping more
Had to reboot a Debian based system this weekend to apply kernel patches
but it would not reboot. All commands (poweroff -p, reboot, init 6)
would return with this error message or similar:
Failed to start reboot.target: Transaction is destructive.
See system logs and 'systemctl status
On Mon, 2 Dec 2019 16:32:59 +0100, Stephane wrote in message
:
> Le 02/12/2019 à 16:03, Mark Hindley a écrit :
> > Did you mean no you don't have elogind installed?
>
> It's in status "p" in Dpkg
> >
> > If so, what are you using? pm-utils?
>
> Apparently yes
> For example, "pm-suspend"
Stephane Ascoet writes:
> Le 02/12/2019 à 15:23, Mark Hindley a écrit :
>> Are you using elogind? If so you can change the defaults in
>> /etc/elogind/logind.conf.
>
> Thanks for the answer but no, and it happens even in TTYs, so I assume
> it's the set at a low-level in system
Hmm, also
On Tue, 3 Dec 2019 08:58:10 +0100, Denis wrote in message
<20191203075810.twxmme6ayyccbftf@reflex>:
>
> dear Massimo,
>
> you are very welcome :^) I'm happy to see here a fellow VUA :^D
>
> down to business
..thanks for talking good sense here, Denis and Massimo. :o)
>
> > If (assuming
dear Massimo,
you are very welcome :^) I'm happy to see here a fellow VUA :^D
down to business
> If (assuming that) we are going to lose the source of init scripts
> upstream, then it's the only way forward. (For those who consider
> recognizing the unit files as a valid source a defeat: I
On Sat, 30 Nov 2019, Hendrik Boom wrote:
> On Fri, Nov 29, 2019 at 07:21:54PM +0100, Massimo Coppola wrote:
>
> >
> > If (assuming that) we are going to lose the source of init scripts
> > upstream, then it's the only way forward. (For those who consider
> > recognizing the unit files as a
12 matches
Mail list logo
