Slashdot Mirror
Security Updates Released for Debian 8 and 7 (debian.org)
An anonymous reader writes: The Debian Project just released Debian 8.5, which adds 65 security updates to the stable release. They're also releasing the final update to Debian 7 (codenamed 'wheezy'), which includes "all other security updates released during the lifetime of 'wheezy' that have not previously been part of a point release."
They're emphasizing that each of the new updates "does not constitute a new version...but only updates some of the packages included. There is no need to throw away old...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."
They're emphasizing that each of the new updates "does not constitute a new version...but only updates some of the packages included. There is no need to throw away old...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."
As I write this, this story has been on the front page for nearly and hour, and there are 13 comments to this story, but none are being shown by default. I thought it was a bug with Slashdot at first. But after changing the threshold to -1, I see that there are in fact 13 comments, it's just that they're all at 0 or lower!
While some are obviously useless comments [like that one] that were rightfully modded down, at least two civilized/on-topic/relevant/informative/insightful comments [that one and that one] have been modded down to -1 for some unknown reason.
Something is clearly wrong when a story has 10+ comments, yet none are shown by default, and the ones that should be shown were inexplicably modded down to -1 for some reason. It bugs me that I now have to browse at -1 to see any comments at all, especially good ones that should have been modded up! The whole point of me coming to Slashdot is to see the comments!
Most recent on slashdot was breaking the backgrounding of processes.
Which is disabled by a simple option in the config file. Which Debian has done, btw.
My product had our (once) portable init script broken in RHEL7.2 by a systemd change that now declares that the init.d script cannot be a symlink to the product installation area
Really? Are you sure? I just tried that and it works.
My product had our (once) portable init script broken in RHEL7.2 by a systemd change that now declares that the init.d script cannot be a symlink to the product installation area.
This was a bug that had been fixed: https://github.com/systemd/sys...