News for hackers. Stuff that matters.
Re:Slackware 14.2 release candidate 1 by ktRolster on Friday March 18, 2016 @02:42AM (#11310302)
I don't see systemd in there anywhere.
Re:Slackware 14.2 release candidate 1 by Tomte on Friday March 18, 2016 @03:07AM (#11310352)
Patrick Volkerding is hesitant about systemd, but not openly hostile, so he has decided to stay away from it for now, but hasn't ruled it out for the future.

People who are set against systemd should probably better look elsewhere (although their options are pretty limited).

Re:Slackware 14.2 release candidate 1 by bitwize on Friday March 18, 2016 @07:46AM (#11311108)
Alternatives include CRUX (whose maintainer's systemd stance is "over my dead body :)"), Void Linux (the only distro I know of to adopt systemd by default and then migrate away from it; currently it uses runit with systemd as an option), and Alpine.

I'm sticking with Slack for the time being, but I've got my eye out for alternatives should the worst happen.

Re:Slackware 14.2 release candidate 1 by digi_owl on Friday March 18, 2016 @09:23AM (#11311585)
> to adopt systemd by default and then migrate away from it

Now that could be a interesting read, if documented somewhere.

Re:Slackware 14.2 release candidate 1 by jff on Friday March 18, 2016 @11:34AM (#11312427)
I've also played a little bit with Devuan, which is basically just Debian without systemd, and it seemed to work pretty well.
Re:Slackware 14.2 release candidate 1 by bitwize on Saturday March 19, 2016 @12:51AM (#11317370)
To be quite honest I didn't have much faith in Devuan as lasting beyond the "publicity stunt" phase, so it's remarkable to me that it's still around.
Re:Slackware 14.2 release candidate 1 by morb on Friday March 18, 2016 @08:55AM (#11311432)
Because you weren't supposed to see it there. Because it was never announced. Because it was never planned to be in there.

It might happen in the future, but as of now Slackware (and Gentoo) are those distros that don't have systemd. Some people might like it for that.

Re:Slackware 14.2 release candidate 1 by jqm on Friday March 18, 2016 @09:55AM (#11311775)
It's Slackware. You have to put systemd in yourself:)
Re:Slackware 14.2 release candidate 1 by digi_owl on Friday March 18, 2016 @07:24AM (#11311039)
To get systemd working you need PAM, and Slackware has yet to ship a release with PAM enabled.
Re:Slackware 14.2 release candidate 1 by jkljkljkljkl on Friday March 18, 2016 @12:06PM (#11312694)
There's no PAM in CoreOS, which uses systemd.
Re:Slackware 14.2 release candidate 1 by digi_owl on Friday March 18, 2016 @12:55PM (#11313076)
And this is why discussing anything systemd is such a pain.

Apparently you can forgo systemd_pam (a poor naming choice, given the following) if you do not use logind. And logind is used for seat and session tracking, something CoreOS likely have no need for as it is meant to handle containerized servers.

Yet all this is in systemd the project, because systemd is the swiss army knife of Linux user space.

So yes, Slackware would likely need to adopt PAM if they want to adopt systemd.