In the opinion of this 'end user,' 13.1 has been the most "trouble free" release I've used to date.

Agreed.........just installed it on a HP Pavilion dv7-3186cl, only thing I had to do after install was to get the Slackbuilds for my Broadcom WiFi.

Absence of HowTos for various wireless adapters, ndiswrapper configuration etc. A hardware list of wired/wireless adapters which work or doesn't work out of the box are welcomed.

A LiveCD for testdrive before an upgrade.

I don't miss that in Slackware and now that we have slackpkg, things are even easier. I don't miss "automatic upgrade" either, and slackpkg is good enough at presenting you the proposed upgrades.

I have installed some other distributions recently in virtual machines and IMHO apt, yum and urpmi e.g. are not that bad, but dependencies problems which arise as soon as you begin to install "non official" packages for your distributions are not easily sorted out.

I like to be able to check (and modify if needed) the Slackbuild before making a package (think of what occurs when the package does some nasty chmod).

I don't like the bad habit of other distributions' packagers to cut software in thin slices and/or patching or "customizing" it only to look smart. For instance shipping some-package and some-package-dev separately, or stripping Firefox from its xulrunner internal engine.

To people complaining about having to install everything then remove what they don't use: unless you be really short on disk's space, why do you need to remove anything ?

I only wish we could have some more packages, in an official repository as space is limited on a DVD, e.g. corresponding to those among the slackbuilds available @ slackbuilds.org that do not depend on anything not included in a full Slackware install.

Huge thanks to Pat and the Slackware team.

I arrived at the end of 12.2 and upgraded to 13 and had nothing but troubles until I got lucky and it all came together...then along came 13.1 and lo I am struggling to get it up and running again...
Well thats what I like about Slack its making me *learn* but at the cost of being a complete and utter Slacker... LOL

0 members found this post helpful.

You're the one sniveling about the number of errors. It's not my job to prove your point.

0 members found this post helpful.

packages are hard to come by, and getting dependencies is sort of a hassle.

I think making your stance on things once is good, twice is pushing it but thrice is superfluous. Please cut it out.

0 members found this post helpful.

You must surely mean "pre-compiled packages" and their dependencies - ?

What I don't like about Slackware, is that I have no complaints about it, .

I just stumbled across this thread and read all posts.

My first inclination was to post some "clever" remark, but that is beyond my mental abilities today!

Then I thought - seriously - what one thing do I not like about Slackware? If there were one thing I could change, what would it be?

... I am stumped!

Some things mentioned negatively by others, are things I love about Slackware!

Lilo is the default boot manager - I love lilo and cannot think of a singly grubby replacement that I would prefer! I know lilo is getting stale, but I see no reason to change in my lifetime!

No package dependency checking - again, this is a valuable feature! The slackbuild approach is simple, elegant even, the perfect approach in my (much under-rated) opinion!

So, after some serious thought - I would not change ANYTHING about Slackware, except post-install! But that is the way it should be, and that is why Slackware is perfect!

Agreed! I just completed an install of Slackware 13.1 on my little Toshiba NB200 Netbook. Install went without a hitch. Installed wicd and it found my encrypted home wireless network instantly.
I love Slackware!

Bit late on the spanking there Those posts were from Feb 2010 =)

Trolls looking for a fight on the "official Slackware" forum

Well I'm a faithful Slackware follower and I could probably list several things I don't like about Slackware if I put my mind to it. Constructive criticism is always helpful or at the very least interesting. That being said these things tend to devolve into flamewars but the thread itself is fine IMO.