After 13 years the Debian-Administration website will go read-only at the end of the month. Then later in the year it will transform it into a solely static-site so that the articles, weblogs, and associated comments are not lost - and they can be served via single server or two. Mostly this is happening due to lack of new content being added and folks posting more elsewhere.
https://debian-administration.org/article/730/This_site_is_going_to_go_read-only
(Score: 0) by Anonymous Coward on Saturday September 16 2017, @10:00AM (2 children)
really stable?
s/Debian/Slackware/g
(as I've had far more Debian servers screw up on me than Slackware ones over the years..that's both monumental fubars and stupid little fuckups when various updates were applied)
(Score: 3, Informative) by Anonymous Coward on Saturday September 16 2017, @12:59PM (1 child)
"Stable" doesn't just mean it doesn't crash. It also means it gets timely updates, especially when there are security issues discovered. It also means it's extensively tested by a wide base of users. Debian offered far more of those things than Slackware ever could have.
(Score: 0) by Anonymous Coward on Saturday September 16 2017, @11:45PM
Slackware used to be entirely put together by one guy, who didn't care one iota about security. Last time I looked into it, I saw that that has changed for the better.
Most security flaws transcend Linux distributions (some affecting BSD too). You could keep an eye on the Debian security advisories while running Slackware, to be aware of the times when you're running unpatched software. The converse applies too: Slackware's advisory [slackware.com] about CVE-2017-7526 predates Debian's [debian.org] by nearly a month.