Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
They are really like the same. I can describe Arch as a Slackware with Pacman. Slackware doesn't have a package manager that handles dependencies. With Slackware you'll spend a lot more time installing and updating software, that's it. Other than this fact - it's hard to notice any real difference.
Arch is a rolling-release, you don't get Arch 6 or 7, etc. You install the latest release, then that is constantly updated - forever, hopefully. Slackware has two versions, the stable numbered release (now 13.37), and current. The stable release only gets security updates to its software, whereas current is where new software or newer versions of software are tested for the next release. Thats roughly it.
Not as obvious but a few things to consider documentation is amazing for arch not sure about slackware as I haven't used it in years but I'm guessing the community feeling is slightly different as with any distribution. Already mentioned but one of the best things about arch is always current and rolling released. Both require you read and learn a bit of what you are doing. Slackware is way older than arch if you're looking at length of time being around. Sorry for any typos writing this on my phone.
There's quite a lot of documentation out there for Slackware. See the link in my signature. Useful stuff for Linux in general, too.
I like Arch. Tried it a while ago in VirtualBox, and I've got ArchBang in VBox now.
I have been using both for awhile now, and most of my ARCH installs sometimes "break" or something goes wrong with Pacman, especially if running testing, except for my ArchBang install, which has never broken so far.
So, IMO Slackware is far more stable than any other distro and gives the user the freedom to do whatever, and the big plus is that creating your own packages from source, etc on Slackware is much easier than other distros.
When you install Slackware, you install a fully functional distribution with a complete software load. You may choose to add additional software and many Slackers do, but you have all you need to hit the ground running.
With Arch, you build your system piece-by-piece, installing only what you want. When you first install Arch, you have a terminal. It's up to you to install X, a window manager, etc.
I started with Slackware. From time to time I've strayed, but I've always come back.
With arch it's difficult (impossible) to add things unless you're connected and stay connected.
I've kept my arch setup disconnected for almost a year went online read the announcements and updated accordingly. Not impossible or difficult but yes it does work better when online and you in general want to do the initial setup online but as mr alex said it's not required.
When I try a distro, I always run the main programs from a terminal to see what Bash has to say. The last time I tried Arch (2010), Firefox alone gave 23 warnings, 6 labeled critical. You don't get that in Slackware! As I said in my review, "After a day's work I had a GUI, 3 applications, and a dead Alt key."