In case you do not look it up here are a few snippets:
(Alien Bob Slackware Contributor):
"Some things will probably be forced upon Slackware - PAM has been on the
"carefully circumventing but you never know" list for a long time. PAM is not
bad to have at all, but it is personal opinion of the Slackware boss which
keeps it at bay. That is an architectural decision which we can live with as
a team and as Slackware users.
But systemd is essentially evil. It is invasive, extremely hostile to other
environments, threatening to kill non-Linux ecosystems which have hal, udev,
dbus, consolekit, polkit, udisks, upower and friends as dependencies. And
every iteration of the software written by the Redhat employees who are
responsible for hal, udev, consiolekit, polkit and now systemd are
incompatible with previous releases, re-implementing their bad ideas with new
bad ideas... basically proving that these Redhat employees must be declared
unfit to work on the core of a Linux distro.
However, the influence of their employer is so big that these products are
forced upon the wider UNIX community and at some point it will be "assimilate
or die". I hope we (Slackware) will find a way where we do not have to
assimilate but still manage to keep the distro working. I have high hopes for
KDE which has no Redhat ties and so far, manages to stay clear of this mess,
sticking to widely accepted standards.
An example of impending doom: udev sources for recent releases are no longer
in existence. They are now part of systemd source tarballs. And udisks? That
has been deprecated in favour of the new "udisks2". Read
http://igurublog.wordpress.com/2012/...loss-for-linux and weep.
Eric"
