Just to tidy up after mwdecavia (yes, his post was off-topic but that's no reason not to close it down and tidy up the loose ends):

I followed all those "clues" that he provided individually, just to set my mind at rest. Most of them were ultimately references to the symbolic link to elogind in the /run directory. For example, the current working directory of PID 1 is /, so /proc/1/cwd/run is just /run. And there's that link again. It's elogind pretending to be systemd for the benefit of any software (cups for example) that expects systemd to be around.

The one exception that I found was some actual systemd headers in /usr/include/elogind/systemd. But headers are inert; they don't do anything to to your system. They're clearly there for the benefit of people who want to compile something that expects systemd to be on the machine. Again, it's elogind in wolf's clothing.

All clear! There's no systemd in Slackware.

2 members found this post helpful.

Is elogind really that needed on slackware ?
Can't you do with xdm / sddm etc ?
I personally use xdm.

Yes, it is required if you use KDE.

Actually it is only required because of certain references and "requirements" that have been entered into the KDE source referencing SystemD features or services. If someone has the time and motivation to revert all of that pointless cruft then neither EloginD nor SystemD would be required. IF you MUST have one, EloginD is far less problematic compared to SystemD.

Personally I have not the time or energy to re-maintain KDE after it leaves the developers release, so I can live with EloginD. I will be happy when/if SystemD just goes away and we can stop dealing with the silliness!

1 members found this post helpful.

Error...