Debian 8.7 Released (debian.org)

Debian 8.7 has been released. An anonymous reader quotes Debian.org: This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems. Security advisories were already published separately and are referenced where available. Please note that this update does not constitute a new version of Debian 8 but only updates some of the packages included.

There is no need to throw away old "jessie" CDs or DVDs but only to update via an up-to-date Debian mirror after an installation, to cause any out of date packages to be updated. Those who frequently install updates from security.debian.org won't have to update many packages and most updates from security.debian.org are included in this update.
86 packages have been updated -- including some fixes for systemd. ("Rework logic to determine when we decide to add automatic deps for mounts; various ordering fixes for ifupdown; systemctl: Fix argument handling when invoked as shutdown...")

Comments

Re:One can hope

[sjames]

The old pile of shit was willing to keep its fingers out of other people's pies if you wanted to try something else along side it.

It also understood imperatives. If you tell it run something NOW, it does just that, every time.

Re:One can hope

[Motherfucking Shit]

More importantly to me, I've used the old pile of shit for 20 years. I know how it works, I know its quirks and shortcomings, and I'm comfortable with all of that.

I have no particular aversion to trying new things. I ran ntpd for years, now I use chrony. I ran exim for years, now I use postfix. I ran apache for years, now I use both apache and nginx. I ran cvs for years, then svn for years, and am now aboard the git train. I was able to gradually step through all of those changes and take time to learn them properly. And when something went wrong along the way, the problem was isolated and I could troubleshoot it in isolation.

systemd on the other hand wants to implant itself underneath every aspect of the OS like a kludgey layer of Elmer's paste, where even such basic functionality as DNS resolution wants to worm its way through an unnecessary and complex intermediary service. Not to mention that when systemd goes tits up, it has a tendency to take the entire machine with it.

No thanks.

Re:One can hope

[Anonymous Coward]

Do tell one reason how Systemd has actually helped something?

Systemd has helped raise awareness of the *BSDs.

Many former Linux desktop users who were driven away by systemd have ended up using FreeBSD. Many who ran Linux servers have started using OpenBSD instead. Those who ran Linux on older or less-powerful hardware have discovered the joys of NetBSD.

Systemd has turned out to be one of the best advertising campaigns for the *BSDs.

Re:One can hope

[nadaou]

What was a better way, the UNIX way, was having multiple interchangeable options for any particular cog in the machine. No reliance on a sole supplier. In Debian even HURD or BSD could be swapped out for the Linux kernel in a semi-official, if experimental, way.

Avoiding a mono-culture has huge industry implications for surviving horrific infrastructure bugs, engaging competition and A/B tests, and filling niches with the best tool for the day's particular job. If systemd was truly optional in official Debian there would be no crisis, no endless talking past each other hate filled forum threads. Instead there was an unfortunate slim-vote by a Debian technical committee and major community damage to the project with a large number of DDs and contributors losing passion for the greater project. Which is the real horror and tragedy of the thing.