Good news. It seems that the Slackware website saga has come to a happy ending. According to the -current changelogs, the old code has been updated:
Sat Jun 2 01:03:42 UTC 2012
As you’ve possibly noticed by now, slackware.com is back on the air, and
I’d like to take this opportunity to give a hearty thanks to Mark Post of
Slack/390 fame for updating the PHP code to make it happen! Eric Hameleers
and the rest of the crew also pitched in to help get it installed and
running on our other server. Thanks as well to all the folks who emailed
with offers of hardware, help porting, and other support for the site.
We really appreciated it. Viva la vie Slackware!
I welcome this news with relief. Despite the fact that for some time it has been clear that the problems only affect the website and the project itself is in no danger, the whole situation unnecessarily sidetracked users’ attention from what should matter most, ie. the distro itself. Hopefully, from now on we’ll be able to focus entirely on the development of the current branch. If you look at the changelogs, recently there have been quite a few udates.
Today’s bunch of updates brings a new little tool called iftop which, according to its website, is a network equivalent of the top command.
iftop does for network usage what top(1) does for CPU usage. It listens to network traffic on a named interface and displays a table of current bandwidth usage by pairs of hosts. Handy for answering the question “why is our ADSL link so slow?”.
It looks like a handy tool to use with the conky output.