6 ms·

I don't see systemd in there anywhere.

Tomte 11y ago
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).
- bitwize 11y ago
  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.
  - digi_owl 11y ago
    > to adopt systemd by default and then migrate away from it Now that could be a interesting read, if documented somewhere.
  - jff 11y ago
    I've also played a little bit with Devuan, which is basically just Debian without systemd, and it seemed to work pretty well.
    - bitwize 11y ago
      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.
digi_owl 11y ago
To get systemd working you need PAM, and Slackware has yet to ship a release with PAM enabled.
- jkljkljkljkl 11y ago
  There's no PAM in CoreOS, which uses systemd.
  - digi_owl 11y ago
    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.
mlvljr 11y ago
http://forums.debian.net/viewtopic.php?f=3&t=126148&sid=83bf2b5844dbcc4096384b198b677158&start=15 http://forums.debian.net/viewtopic.php?f=3&t=126148&sid=83bf...
morb 11y ago
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.
jqm 11y ago
It's Slackware. You have to put systemd in yourself:)

Tomte 11y ago

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).

bitwize 11y ago
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.
- digi_owl 11y ago
  > to adopt systemd by default and then migrate away from it Now that could be a interesting read, if documented somewhere.
- jff 11y ago
  I've also played a little bit with Devuan, which is basically just Debian without systemd, and it seemed to work pretty well.
  - bitwize 11y ago
    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.

digi_owl 11y ago

To get systemd working you need PAM, and Slackware has yet to ship a release with PAM enabled.

jkljkljkljkl 11y ago
There's no PAM in CoreOS, which uses systemd.
- digi_owl 11y ago
  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.

mlvljr 11y ago

http://forums.debian.net/viewtopic.php?f=3&t=126148&sid=83bf2b5844dbcc4096384b198b677158&start=15 http://forums.debian.net/viewtopic.php?f=3&t=126148&sid=83bf...

morb 11y ago

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.

jqm 11y ago

It's Slackware. You have to put systemd in yourself:)