[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian Buster release to partially drop non-systemd support

On Mon, Oct 15, 2018 at 04:18:57PM +0200, Thorsten Glaser wrote:
> Matthew Vernon wrote:
> >I'm aware of some work ongoing at the moment to try and improve matters
> >(currently looking at elongind, for example). If anyone's got some
> What’s elongind? elogind? Never heard of it…

elogind is an isolated part extracted from systemd-logind, maintained by Void
people, and in use by several other distributions (Gentoo, Devuan, etc).  It
is a drop-in replacement for interfaces exposed by libpam-systemd.

I'm using it for several months myself, and intended to package it in
Debian, but had a lack of tuits to do so.

I just started a new job and I think I'll have a small but non-zero amount
of tuits in the evenings, but havent't finished moving and can't comfortably
run anything that needs reasonable VMs (got nothing but a Pinebook with me),
so I can't be of much help -- but if anyone wants to start the work on
elogind, I'll try to do what I can.

> >interest/effort in getting sysvinit (and related bits) in a better state
> >for buster, do drop me a line.
> I’ve volunteered to help out earlier in the thread, within constraints
> (but rather that than to see things go and break).

The main problem with sysvinit is the lack of a git repository.  There's a
massive amount of opportunities for drive-by contributions, but no way to
collaborate doing so.

Then, there are nice-looking new upstream releases of sysvinit (three in
this year, after several years of dormancy), but that'd require some real
testing.  Unlike elogind, it could perhaps reasonably be tested remotely...

⣾⠁⢰⠒⠀⣿⡁ 10 people enter a bar: 1 who understands binary,
⢿⡄⠘⠷⠚⠋⠀ 1 who doesn't, D who prefer to write it as hex,
⠈⠳⣄⠀⠀⠀⠀ and 1 who narrowly avoided an off-by-one error.

Reply to: