Linked by Eugenia Loli-Queru on Thu 4th Dec 2003 04:42 UTC
My husband hooked me up on Slackware almost three months ago (he used to run Slackware in the '90s). While I use a large range of OSes on a daily basis, when I am under Linux I now prefer to use Slackware. This is my mini-article with thoughts on Slackware 9.1 after using it for three months on and off. Ten screenshots are included.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Slackware's been an off-and-on distro for me, between it and Debian. Yesterday, though, Slackware won a major battle, as it's the first distro that's got ACPI working out of the box on my laptop.
And having used apt, I must say, swaret is up to the task. It doesn't have as many packages, and isn't *quite* as slick as apt and all of its helper apps, but with a little more polish, swaret could be quite the trend-setter.
I imagine the installer being upgraded so that it uses swaret as a sort of backend, just for dependancy checking, using the CD's as the packages' source, and happening all in the background. I happen to have a messed up gcc which I started trying to fix about 20 seconds before starting this post. The uh-oh seems to have happened due to an unmet dependancy from when I first installed Slack (yesterday). I don't think I've run in to such a problem before, but I know I've been asked if I wanna install things like grep or gtk before, and always said yes because I'd previously said yes to packages I KNOW depend on it. I've always wondered what would happen if I said no. If swaret was backending the installer, I'd know that nothing "interesting" would happen. And all the while, the installer would behave the same as ever.