SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi. Been using linux for quite some time now but never got to trying out slackware. I've used several fedora's, a few ubuntus and a few live distros. None of the 64 bit versions worked good for me and all of the 32 bit versions (of said distros) have worked for me. Anyway my goals are:
1. to have a striped down desktop like flux and do everything from the cl.
2. to have a (2nd) modern 'heavy' desktop with all the bells and whistles, and maybe extra large vista styled icons for added sarcasm effect.
3. To run at least one video game, preferably WoW.
My expectations...
1. read a lot
2. read a lot
3. learn a lot
4. compile a lot.
Slackware seems like the distro you have to work the hardest at (except gentoo) which is an ironic name if so. However it also seems that will make it the most rewarding to log into. I am guessing the hardest part will be being patient and reading up before an install so that I can get on the internets (sic.) asap. There arent too many slackware books at the local library so once i have connectivity i can hash out any problems online. Not paying attention in the very begining seems to be the most common mistake.
On other distros I have been able to get everything a 'windows' pc can do except video games. I realize a lot of them dont work well (in wine) but I am confident with enough determination and work I can get one or 2 running.
My expectations...
1. read a lot
2. read a lot
3. learn a lot
4. compile a lot.
Welcome to the official Slackware forum:-) I think you're approaching Slackware with the correct attitude. Yes. If you prepare for the initial install Slackware is a straight forward distro to use.
Best wishes with learning. We are here to help if you need a hand:-)
When I switched from Redhat to Slackware, I expected many difficulties too
But in fact, I didn't meet any problems
I admit, I didn't have any exotic hardware and used wired internet connection though
This was in 2003 I think, at this time udev and hotplug did not work very flawlessly
(I remember posting in this forum and suggest disabling hotplug as universal solution for every hardware/module problem other users had at this time, I was even called hotplug hatter by someone )
Check your hardware, do you use wired or wireless internet connection, IDE or SATA hard drive, etc..
Then look through this forum if other user has problem with same hardware, etc...
With modern version of udev/hotplug, installation is very easy nowadays, hardware is usually well recognised
I am guessing the hardest part will be being patient and reading up before an install so that I can get on the internets (sic.) asap. There arent too many slackware books at the local library so once i have connectivity i can hash out any problems online...
Well, I agree that you may have to read, but not really "a lot". I'd say more "read at least something". Really, you don't have to read anything, but it will go much smoother if you read at least about the install process in the Slackbook or other places. It will take less than 10 min and save you a headache in case you get lost.
As for compiling, you don't really have to compile a lot, there are many packages available if you don't want to compile. But, unlike in many other distros, things actually have a higher chance of compiling properly on Slackware, from what I've observed. I know I had problems in most other distros compiling things from source, but in Slackware it just seems to work out more often. Or maybe I just know more now ?
Anyway, good luck. It's really not as difficult as you might expect.
Bear in mind that Slackware is not designed to provide much hand-holding and is not designed with presumptions about what end-users want. You get a solid base operating system but almost all tweaking is up to you.
How much you struggle depends upon your background. Even with a positive attitude, a lack of basic computer skills will frustrate any person with any operating system, let alone Slackware. If you are a point-and-click user who never "lifts the hood," then likely you will be frustrated. If you are a user who regularly "changes the oil and wiper blades," then probably you will get along fine.
You can download VirtualBox and run Windows in a virtual machine. I run several virtual machines, including a Slackware Current box where I test things.
Actually, I desire to compile. I did not have to compile a single thing in Ubuntu. I haven't since I ran Fedora, and its a skill that I would like to have.
Yes, I get all up under the hood. When I use windows I use things like regedit and services.msc and actually use the command line from time to time. My most recent travels found me installing hal.dll from live linux after a registry cleaner cleaned a bit much. My first PC was an ADAM that I propmtly traded in for a c64. The coolest thing I have done with linux so far is make a script that counted down bottles of beer on the wall for every command entered into the command line.
I will look at the ISO in detail and check out slackbook. Seems like a good place to start. I did check online and the entire library system in the city of pisstburgh has ONE slackware book, slackware for dummies circa 2000.
Quote:
there are many packages available if you don't want to compile.
That is interesting, didnt know slackware had packages. You guys really are slackers.
That is interesting, didnt know slackware had packages.
My god, you really need to read that Slackware Book first!
See http://slackbook.org/ (Slackware Essentials, i.e. the official book which ships with Slackware) as well as http://slackbasics.org/ (Slackware Linux Basics) for two good references (and read them in that order).
Slackware seems like the distro you have to work the hardest at (except gentoo) which is an ironic name if so.
Initially I thought the same. Over time it really does switch to becoming one of the easiest distros to install or maintain. IMO, as long as you take the time to read Pat's notes & directions, Slack is so easy compared to other distros. Which is a good thing, since I've become so busy over the last few years I don't have time for a distro that isn't solid.
And then, after that, it gets fun....But I run it all the time on my KDE desktop w/wine on a nvidia 9600GSO. Framerates are about 20+% faster than on Vista64...Gotta love it.
Except for wireless, when i installed 12.2 it worked "out of the box" on my laptop. I was pleasantly suprised.
I updated to 13 last night and it also went smoothly. I'll be tackling wireless tonight!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.