Now that you have proved yourself to be a complete and utter troll and with you so obviously having lost this argument I won't bother to waste any more time on you, since you are clearly a lost cause.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
It does receive security updates, you have admitted as much yourself. Perhaps you could back your claims up by listing a package found in the stable that is known to be insecure. Have fun searching.
Stuff like this doesn't inspire any confidence whatsoever. "A few days" has turned into a year.
The best you can do is link a page written by an equally uninformed user? Nice evidence. The poster doesn't even know about slackpkg being part of Slackware. No need to manually download and install packages, or use a web based package browser. Slackpkg does all of this for you.
SUSE used to have a site called Webpin that allowed you to search through the contents of packages that broke around the release of 11.4. Yet even openSUSE 12.1 the menu item is still listed.
And remember - this is the recommended package browser linked to from the slackware.com home page.
And remember - this is the recommended package browser linked to from YaST, SUSE's official package manager. Tell me how is this different??
Your obsession with this online 'package browser' is slighlty odd. It is just a contributed nicity. Not an official part of the project. If you want to search the contents you use slackpkg (like a Debian/Ubuntu user would use apt-cache or apt-file). If you don't have Slackware installed yet, look at the MANIFEST and FILELIST files within the directory structure on your mirror of choice.
As a side note, SUSE used to have a site called Webpin that allowed you to search through the contents of packages. There is even a Webpin menu item in YaST (SUSE's official package manager). Then out of the blue around openSUSE 11.4, Webpin stopped working and was no longer maintained. Yet even in openSUSE 12.1 the menu item is still listed.
So tell me, do you go around claiming that SUSE is dying as well?
Updates to -current happen in spurts after much internal testing by the core team. Updates to stable happen only if there is a security problem with a packages. The Moz updates are due to security fixes in their releases. Also Slackware itself doesn't have that many packages comparative to distros like Debian. So what you see isn't bad at all and largely expected.
It may come as as shock to you if you use a distro that is forced on a regular release cycle and hence ships with lots of broken packages because it will need constant updates just to get it working. This isn't the same with Slackware. It is stable so needs very few updates, pretty much security only. That is one of Slackware's primary benefits. Your problem appears to be ignorance.
LibreOffice is not included in Slackware's official repositories, so you are just talking crap there. The most popular third party repository is SlackBuilds It has the latest version: http://slackbuilds.org/repository/13.37/office/libreoffice/
Since May 13 2011 until now, -current has had 728 packages rebuilt, upgraded or added. 435 of those have been within the last 2 months.
My source? http://ftp.uninett.no/linux/slackware/slackware64-current/ChangeLog.txt (a decent mirror if you are looking for one)
The link you provide is equally uninformed since it stated,
"Slackware does not have an apt-get (Ubuntu), portage (Gentoo), or some other variant to allow automatic pulling from an approved repository. Instead, you browse and download
Yet it does have such a tool. It is called slackpkg and it is included in the default install. In many ways works slackpkg works just like apt, other than not automatically dealing with dependencies.
When the next release does come out (and it will) perhaps would you care to post back here to admit your mistake. Since I'm guessing it would be a little hard for you to swallow your pride and do it right away
Please update your list - slackware is dead. No new release in more than a year, the "updated package browser" that was supposed to take a couple of weeks has also been missing in action for more than a year, the server has had many outages (it's currently responds to pings, but no page loads), and the few mirrors don't have much in the way of security and other updates (2 - 3 dozen packages in the last year, depending on the mirror).
I haven't logged in to
Yes there have been issues with the websever running Slackware but this bears little or no relation to the project itself. People don't receive updates from www.slackware.com, they get them from the various mirrors. These mirrors are generally the same ones hosting other popular distros.
If you want further evidence, see PatVs own comment here on
We have you with your two digit UID and Darth just above with his 5 digit UID. Who next?
It doesn't need uPnP but services can use it if it is there.
Hence you could change that to, "Just... don't enable the Unite feature."
Opera and Google are both able to accurately work out the size of their own user base using unique auto update hits. This would seem like a more conclusive method than your own. With this in mind Opera still has a third more users than Chrome globally.
The slashdot summary reads "With the arrival of FireFox 3.5, Safari 4 and the new betas of Google Chrome, browsers support some great new features including canvas and the new audio/video tags".
The original summary from the linked site reads, "With the arrival of FireFox 3.5, Safari 4 and the new betas of Google Chrome and Opera, browsers support some great new features including canvas and the new audio/video tags".
Why has the poster or Timothy gone to the trouble of editing out 'Opera'?
An early employee yes, an he worked with the two founders previously at Telenor but he is not one of the founders himself.