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.
The basic slack install is indeed stable, because slack doesn't use alpha versions in its release, but after that, it is up to you. If you install a development kernel or a alpha version of gnome, kde or dbus there's no telling how (un)stable your system will be.
This statement is valid for speed as well, the standard slackware installation is lightning fast, but if you install all the fancy *bling* (read: compiz ) it will be just as slow as let's say fedora. On the other side it possible to take ubuntu and slim it down to a very fast system.
There is also another side to not having a package manager, no automatic patches or security updates! This is an important downside, because it takes a lot of time to track down and apply all patches for every piece of software installed on your system.
Besides from that, slackware is the most versatile distro out there, I used it for 2 years (8.1, 9.1 and 10) and was quite happy about it. Slackware is absolutely the purest linux, but I exchanged it for debian, which has in my opinion all the upsides of slackware plus the package manager.
Now I use ubuntu because I simply no longer have enough time to spend on maintaining my system, but I still like like slackware.
Not if you want your security updates and patches to be installed. Often I quickly need to install a piece of software and don't have the time to search for all the dependencies and compile the sources. The fact is that I no longer use slack because those things take too much time.
Of course, if you never install updates and you have a stable set of tools, so you don't often have to install new software, it is possible that maintaining your system won't take much time.
If I would put some Linux on my computer it would be Slackware.
Slackware teached a lot about Linux to me... I currently run solely OpenBSD on my computers but I'm thinking about putting Slackware to my desktop. The lack of 3D-acceleration support is not a good think if your thinking about developing OpenGL programs
I am a new slackware user, and linux user in general, and I chose slackware because:
1. I am Bob Dobbs.
2. I can tell my wife I slacked off all day, and she can't get mad.
3. I figured that, since slackware doesn't hold your hand, that the level of linux experience would be higher in its user base, and therefore, the advice I receive in the slackware forums is likely to be better informed than any advice I would receive in the ubuntu forums from a three day ubuntu user who still tells me to restart.
Last edited by globaltree; 11-04-2007 at 03:05 PM.
Reason: can't psell
Devede (while probably not as powerful as ManDVD) has worked for me as far as converting files of various formats to DVD compatible mpeg2 and generating DVD content/iso files. It also has a relatively short dependancy list, many of which are good to have in place anyway.
Thanks for the heads-up about DeVeDe! I will certainly look into it. I'm using convertxtodvd under wine right now so I can at least get my work done while I put together a native-Linux solution. I don't like running Windows apps on my nice new Slackware install but if it preserves my sanity AND keeps me from chucking the whole lot out the window, then I feel it's a good thing. And I did pay 40 bucks for the license so I might as well use it if I can.
It is also a huge relief to hear that even yourself (a savvy Slackware user) gets frustrated with dependencies from time to time. It makes me feel not so much like an idiot. So thanks for that.
In response to the original question though... Slackware really IS a lot to handle for folks like me who are new to Linux altogether. But to be honest, once I got to a certain point it just kinda got under my skin and I couldn't give it up. So now I'm forced to learn as I go. The advantages of Slackware far outweigh the disadvantages.
I currently run solely OpenBSD on my computers but I'm thinking about putting Slackware to my desktop. The lack of 3D-acceleration support is not a good think if your thinking about developing OpenGL programs
While being OT, DRI support under OpenBSD is actually being worked on.
I don't see what his problem is. He's had a few heated arguments with a few members and now he hates everyone who populates this forum. I was going to try to say 'calm down man', but I don't think it'll work.
The advantage I see is that is is just a unix system.
With other distros, You get megabytes of scripts providing everything other distros think you will need, and they are always wrong about that. Then you get regular (poorly tested) updates which can and have screwed up my box more than once. /usr/bin/vi is a symlink to /etc/vim-alternatives/something which eventually tries to run /usr/bin/Vim-iMproved :-\. Red Hat patches as it sees fit and documents these poorly. 15 scripts are run starting X with variables passed from one to the other, so it's a nightmare to follow.
Slackware has less of this, and expects you to be a little knowledgeable or clever. No package management, but 'cat /usr/lib/pkgconfig/sendmail*' gives you the dependencies of sendmail. 'grep spoof.h /var/log/packages/*' tells you which package installed spoof.h, etc. The result is, the system you set up lasts longer, causes less hassle. Which is just as well, because you won't feel like setting it up very often.
The advantages of Slackware for me are many and varied.
Flexibility: I've tailored it for use in embedded digital signage applications, forum servers, weather image servers, development platforms, prototyping systems, and hobby platforms using an amazingly diverse array of hardware.
Stability: this one is well-documented, I mention it only because I am so appreciative and impressed by the approach and attention to detail that Patrick and the rest of the team take on the issue.
Familiarity: I'm intimately familiar with and quite fond of the SVR4 directory structure, shells, and tools that are employed in the distribution. Though it is evolving, so am I (I hope).
I'm using Ubuntu to get my wife familiar with *nix, not so much to wean her from Windows but because she wants to use some of the tools she sees me using and has expressed an interest.
I won't subject her to the deep end of the pool until she has a better handle on the whole picture. I don't see that as an advantage for Ubuntu, its just another tool, good at what it does, as is Slackware.
The result is, the system you set up lasts longer, causes less hassle. Which is just as well, because you won't feel like setting it up very often.
Thing is, I don't even mind setting it up most of the time.
I've had great luck with Slackware setups. I've run it on three different laptops and I don't even know how many desktops, and it remains simple and easy and intuitive to install, and worlds better at hardware support than any version of Windows I've set up.
Most of the time if something's hosed it's my own damned fault, not Slackware's. Like several times when I partitioned things in a stupid way, or when I've forgotten how to do something and end up telling it to do something wrong.
Most of the trauma that comes from setups for me is tweaking KDE to behave the way I like it, and installing the apps I prefer to have on-hand, again not normally something I can blame on Slackware. I'd be doing that on any distro.