Post something that you do not like about slackware
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
About "automatic dependencies checking"
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.
Last edited by Didier Spaier; 06-05-2010 at 04:00 PM.
Distribution: x86_64 Slack 13.37 current : +others
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
In the opinion of this 'end user,' 13.1 has been the most "trouble free" release I've used to date.
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!
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.