Debian considering going systemd init only

mknoop · 2019-09-23 05:01:50

I saw an article in slashdot.org today:

https://linux.slashdot.org/story/19/09/ … -diversity

It sounded like the project director was politely asking the different development teams to work together like grown ups.

If Debian should go systemd init only, will the Devuan development team be able to handle the added work of providing a systemd-free OS still based on Debian? It sounds like it would be a lot more work.

ToxicExMachina · 2019-09-23 08:25:41

I don't see any trouble in that because it's not so hard to maintain existing sysv-rc scripts and make new ones. It will be also fatal decision for Debian because someone will make easy to use tool for generating an initscript for any daemon. Dropping other kernels (kFreeBSD and HURD) will also force developers to work with Devuan instead of Debian.

The real problem is inevitable death of Debian in case of keeping SystemD. The aim of SystemD is RedHat ecosystem. Everything which is not RH-based thing is under attack because SystemD is open source proprietary software (OSPS).

golinux · 2019-09-23 14:46:03

ToxicExMachina wrote:

The aim of SystemD is RedHat ecosystem. Everything which is not RH-based thing is under attack because SystemD is open source proprietary software (OSPS).

And a new acronym is born! OSPS is brilliant!!

yeti · 2019-09-24 05:44:02

ToxicExMachina wrote:

The real problem is inevitable death of Debian in case of keeping SystemD.

Then let's welcome the billions of Debian migrants coming to Devuan!
:-D

Head_on_a_Stick · 2019-09-24 14:11:39

mknoop wrote:

If Debian should go systemd init only, will the Devuan development team be able to handle the added work of providing a systemd-free OS still based on Debian?

The elogind package which is the source of the linked problem was originally packaged up by Devuan and is also used by Gentoo so it should continue to work even if Debian drop it.

ToxicExMachina wrote:

I don't see any trouble in that because it's not so hard to maintain existing sysv-rc scripts and make new ones.

It may not be "hard" but there are currently 1033 packages that ship systemd unit files without matching init scripts[1], they don't currently work properly under sysvinit.

And it looks like some Debian maintainers aren't even testing existing init scripts, let alone adding new ones:

https://lwn.net/ml/debian-devel/b027c97 … 7@bzed.de/

https://lwn.net/ml/debian-devel/2018101 … piware.de/

golinux · 2019-09-24 15:59:16

Head_on_a_Stick wrote:

mknoop wrote:
If Debian should go systemd init only, will the Devuan development team be able to handle the added work of providing a systemd-free OS still based on Debian?
The elogind package which is the source of the linked problem was originally packaged up by Devuan and is also used by Gentoo so it should continue to work even if Debian drop it.

IIRC, Devuan got elongind from gentoo. gentoo didn't get it from us. Maybe I'm misreading . . .

Head_on_a_Stick · 2019-09-24 17:01:19

I think elogind was originally created for GuixSD, adopted by Gentoo and then later packaged for Devuan.

Upstream: https://github.com/elogind/elogind

The version in Debian sid and Devuan beowulf & ceres is now fully ABI-compatible with libsystem0, albeit with most of the functionality stubbed-out.

HevyDevy · 2019-09-25 12:48:21

Hopefully this wont affect my machines, i dont use elogind or consolekit, ive been using devuan with no dbus and it runs great for what i need. Im old school though, we will eventually get left behind and overtaken with tech that is shiny and "progressive" but not really needed.

Last edited by HevyDevy (2019-09-25 12:53:45)

Geoff 42 · 2019-09-25 14:25:56

I have just spotted the latest bit of madness, at El Reg :-

https://www.theregister.co.uk/2019/09/2 … rectories/

He wants to take over your home directory...

Geoff

Head_on_a_Stick · 2019-09-25 17:53:54

Geoff 42 wrote:

He wants to take over your home directory...

If an encrypted laptop is suspended then the key has to be stored in memory, systemd-homed has been created to enable the user password and encryption key to be unified so that the key doesn't have to be kept where a malicious agent can extract it.

So it's a new feature that solves a genuine problem. What a bunch of bastards, eh?

golinux · 2019-09-25 17:58:40

@HoaS
https://refracta.org/docs/readme.refracta2usb.txt

Head_on_a_Stick · 2019-09-25 18:21:10

Thanks for the link, refracta2usb is indeed an awesome tool :-)

But I don't think it solves the problem I explained in my last post, nor does it unify the user authentication data in $HOME so that it can be ported to another machine. And systemd-homed will allow per-user resource constraints as part of the configuration.

fsmithred · 2019-09-25 19:29:56

refracta2usb definitely doesn't solve the encrypted suspend problem. I suppose you could unmount the loopback file that has the encrypted filesystem and then suspend, but I've never tried. I just turn it off if I need it to be secure.

The other problem r2u doesn't solve is the user ID when moving home across different machines. It's meant for a live-usb, so you just take your own OS with you.

The only problem I might have with homed is if it gets in the way of doing things differently. I guess we'll see...

PedroReina · 2019-09-25 21:04:07

HevyDevy wrote:

i dont use elogind or consolekit, ive been using devuan with no dbus and it runs great for what i need.

That seems very interesting to me. Could you, please, elaborate on it? May be a link or a new thread? Thank you.

fsmithred · 2019-09-26 01:49:36

PedroReina wrote:

HevyDevy wrote:
i dont use elogind or consolekit, ive been using devuan with no dbus and it runs great for what i need.
That seems very interesting to me. Could you, please, elaborate on it? May be a link or a new thread? Thank you.

I don't know what HevyDevy is using, but I made some nodbus live isos to see how much I could install. It wasn't difficult, and I got a fairly complete set of desktop apps. You can read about it here:
https://dev1galaxy.org/viewtopic.php?id=2158

Newer isos than the link in that thread are here.
https://get.refracta.org/files/experimental/
(refracta9 is ascii, refracta10 is beowulf.)

HevyDevy · 2019-09-26 09:20:18

PedroReina wrote:

HevyDevy wrote:
i dont use elogind or consolekit, ive been using devuan with no dbus and it runs great for what i need.
That seems very interesting to me. Could you, please, elaborate on it? May be a link or a new thread? Thank you.

I should have said devuan refracta10 nodbus as fsmithred mentions in previous post. Thanks for all your hard work fsmithred and team.

Few caveats for networking, cant use wicd or networkmanager so i just use wpa-supplicant instead, all the old network tools work fine you just have to know how to work them. I use openbox with obmenu-generator, lxdm seems to be fine and doesnt have a hard dependency on dbus as far as im aware so i use it to set the greeter. Firefox seems to be working ok as well.

init─┬─acpid
     ├─clipit───2*[{clipit}]
     ├─compton
     ├─conky───5*[{conky}]
     ├─cron
     ├─dhclient
     ├─exim4
     ├─6*[getty]
     ├─lxdm-binary─┬─Xorg───3*[{Xorg}]
     │             └─lxdm-session───openbox───ssh-agent
     ├─mdadm
     ├─ntpd───{ntpd}
     ├─pnmixer───{pnmixer}
     ├─rpc.idmapd
     ├─rpc.statd
     ├─rpcbind
     ├─rsyslogd───3*[{rsyslogd}]
     ├─sshd
     ├─tint2─┬─sh───firefox-esr─┬─2*[Web Content───22*[{Web Content}]]
     │       │                  ├─Web Content───16*[{Web Content}]
     │       │                  └─63*[{firefox-esr}]
     │       └─sh───lxterminal─┬─zsh───pstree
     │                         └─{lxterminal}
     ├─udevd
     ├─uuidd
     └─wpa_supplicant

Although dbus is not being used it does show up with a dpkg -l | grep dbus, but dbus and dbus-x11 are not installed so not sure what this is about?

~ % dpkg -l | grep dbus                                                    :(
rc  dbus                                 1.12.16-1+devuan2                   amd64        simple interprocess messaging system (daemon and utilities)
rc  dbus-x11                             1.12.16-1+devuan2                   amd64        simple interprocess messaging system (X11 deps)
ii  libdbus-1-3:amd64                    1.12.16-1+devuan2                   amd64        simple interprocess messaging system (library)
ii  libdbus-glib-1-2:amd64               0.110-4                             amd64        deprecated library for D-Bus IPC
ii  libdbusmenu-glib4:amd64              18.10.20180917~bzr490+repack1-1     amd64        library for passing menus over DBus
ii  libdbusmenu-gtk3-4:amd64             18.10.20180917~bzr490+repack1-1     amd64        library for passing menus over DBus - GTK-3+ version

fsmithred · 2019-09-26 13:10:53

The rc before the package name means that the package was installed previously, has been removed and left behind one or more config files. The original iso only has the four libraries listed, so you must have installed something that pulled in dbus and dbus-x11 and then removed it.

To get those two out of the list, purge them. (Note: 'aptitude search ~c' will show you others that left behind config files, and 'aptitude purge ~c' will get rid of them.)

HevyDevy · 2019-09-26 13:42:01

Come to think of it, i believe i may have only installed refracta10 test iso with no X not the nodbus version and then did the apt pinning later on for a no dbus. My other machine had the nodbus version so i was trying to emulate it or copy the configs over to the other one, thank for the info fsmithred.

PedroReina · 2019-09-26 18:44:43

fsmithred wrote:

You can read about it here:
https://dev1galaxy.org/viewtopic.php?id=2158

HevyDevy wrote:

I should have said devuan refracta10 nodbus as fsmithred mentions in previous post.

Thank you. On desktops I'm using now XFCE, so I will need dbus. But for a minimal server your work seems very promising. I'll study it as soon as I can.

bgstack15 · 2019-10-04 18:54:43

I have just been researching how to shut down/restart/suspend a system using python, without dbus, and haven't come up with much. I searched for "dbus" on this forum and came across this thread. I was surprised to learn I have dbus running on my Devuan desktops, even the Fluxbox ones.

golinux · 2019-10-04 20:50:22

Just be thankful that kdbus hasn't made it into the kernel.
http://lkml.iu.edu/hypermail/linux/kern … 04853.html
http://lkml.iu.edu//hypermail/linux/ker … 01331.html

fsmithred · 2019-10-04 21:04:55

cat /etc/sudoers.d/user_shutdown
phred    ALL= NOPASSWD   /sbin/shutdown, /sbin/halt, /sbin/poweroff, /sbin/reboot

No dbus needed. You can make panel buttons for 'sudo halt' and the others if you don't want to type it.

yeti · 2019-10-04 22:05:05

In Linux's toddler days we had halt, reboot and shutdown logins with these commands as shell.

Head_on_a_Stick · 2019-11-17 10:33:19

The GR is now up for discussion with three options on the table:

https://www.debian.org/vote/2019/vote_002

HevyDevy · 2019-11-17 11:39:06

Head_on_a_Stick wrote:

The GR is now up for discussion with three options on the table:
https://www.debian.org/vote/2019/vote_002

There should be a 4th option.

4) drop systemd as init and revert back to SysVinit.

Wouldn't that throw a spanner in the works!

The officially official Devuan Forum!

#1 2019-09-23 05:01:50

Debian considering going systemd init only

#2 2019-09-23 08:25:41

Re: Debian considering going systemd init only

#3 2019-09-23 14:46:03

Re: Debian considering going systemd init only

#4 2019-09-24 05:44:02

Re: Debian considering going systemd init only

#5 2019-09-24 14:11:39

Re: Debian considering going systemd init only

#6 2019-09-24 15:59:16

Re: Debian considering going systemd init only

#7 2019-09-24 17:01:19

Re: Debian considering going systemd init only

#8 2019-09-25 12:48:21

Re: Debian considering going systemd init only

#9 2019-09-25 14:25:56

Re: Debian considering going systemd init only

#10 2019-09-25 17:53:54

Re: Debian considering going systemd init only

#11 2019-09-25 17:58:40

Re: Debian considering going systemd init only

#12 2019-09-25 18:21:10

Re: Debian considering going systemd init only

#13 2019-09-25 19:29:56

Re: Debian considering going systemd init only

#14 2019-09-25 21:04:07

Re: Debian considering going systemd init only

#15 2019-09-26 01:49:36

Re: Debian considering going systemd init only

#16 2019-09-26 09:20:18

Re: Debian considering going systemd init only

#17 2019-09-26 13:10:53

Re: Debian considering going systemd init only

#18 2019-09-26 13:42:01

Re: Debian considering going systemd init only

#19 2019-09-26 18:44:43

Re: Debian considering going systemd init only

#20 2019-10-04 18:54:43

Re: Debian considering going systemd init only

#21 2019-10-04 20:50:22

Re: Debian considering going systemd init only

#22 2019-10-04 21:04:55

Re: Debian considering going systemd init only

#23 2019-10-04 22:05:05

Re: Debian considering going systemd init only

#24 2019-11-17 10:33:19

Re: Debian considering going systemd init only

#25 2019-11-17 11:39:06

Re: Debian considering going systemd init only

Board footer