A Few Days With Arch Linux
By Dennis Wyman on November 13, 2009 12:49 PM | Permalink | 5 Comments
However, despite the fact that every server I work on runs Linux (typically CentOS or some flavor of BSD) none of my home or business computers do. At the office, there's a couple Linux boxes that I'm tasked with maintaining, but none of my own PC's actually run it.
In fact, my experience with Linux as a desktop computing solution has been largely negative. Most pre-configured distros these days come with a lot of extra crap that bogs down your system, especially older systems. You could run an older version of a major distro, but then you run the risk of having unpatched software vulnerable to all sorts of security risks. Even lightweight distros come with unnecessary extras or are configured all weird so if you attempt to change shit and you don't know what you're doing, you can fuck your entire system up.
This is especially a problem if you're still just trying to learn Linux and you have no idea where to start, because you start working with the pre-configured GUI, which as for anybody who knows even just a hint about Linux, is NOT what you want to become accustomed to if you plan on using Linux even only somewhat effectively.
Then I discovered Arch.
Arch Linux, which brands itself as "A Simple Lightweight Linux Distribution," is exactly that. Included in the basic CD images is the core Operating System, VIM (an awesome text-editor) and Pacman, a simple Package Manager that connects to their online repositories so you can get extra software as you wish. And that's it.
The beauty of Arch is you configure it yourself, from the very start. If you are only vaguely familiar with how to use command line, you'll have a much greater understanding of how it works after you've built your entire OS and desktop from the ground up. To top it all off, their Wiki is one of the best software Wiki's I've ever had to refer to for assistance, as every aspect of the core OS and how to set it up is exhaustively documented with step-by-step instructions.
The other thing I love about Arch is it gives you the ability to setup a fully-fledged usable OS on an older computer. My 2.2 Pentium 4 laptop with 512MB of RAM slows to a crawl trying to run any distro that comes with GNOME or KDE. (See: Pretty much all of them) With Arch, I was able to build the basic OS, and install extra components as I needed them. There was no having to remove extra crap I didn't need, because "extra crap" wasn't there in the first place. No messy GNOME purges trying to install a lighter desktop environment. I know every single folder and program that is on my drive because I built it from scratch, and that was with having only a very modest understanding of Linux to start with. I even have a fully-fledged desktop environment in the form of LXDE, which is basically the Openbox window manager with a couple extra tools. And it runs incredibly zippy; even faster than a bare-bones Windows XP install ran on it, which was much more memory- and CPU-efficient than any major distro pre-packaged with GNOME or KDE.
I had a bitch of a time trying to get the X Window System trying to run on my laptop, which is to be expected when installing it from the ground up for the first time with no prior experience. (Hey, why would I need to run X on a webserver? I had literally never touched it before.) But once that hurdle was passed, it has been very smooth sailing. There is a lot of available software through the Pacman repositories just to start with, and even for stuff you can't snag through Pacman it's not like it's hard to compile a tarball. And I can always take solace in the fact that I know every single thing that is on my system, and walk away having learned a bit more about the inner-workings of Linux.
My main desktop is likely to stay running Windows XP as it's primary OS, since I also use it heavily for graphic design, gaming and multimedia purposes, which is far from Linux's strong points. (Plus XP is stable and I have had no major complaints about it.) But for a laptop that will enable me to easily manage web servers from a remote location, quickly edit pages and browse the web, it's perfect. Plus I can install (and have installed) XAMPP so when I'm parked at the office, it can double as a local testing server before deploying sites live. Score! And keeping with the "Keep it simple" philosophy that Arch employs, the XAMPP services only run when I tell them to, controlled via a simple service, so there isn't an entire web server running in the background taking up resources if I don't need it to.
So three days into using Arch and so far I am very pleased. Very pleased. If the "major" distributions such as Ubuntu have you turned off Linux because of bloat, I definitelly recommend giving Arch a spin if you aren't afraid of getting truly down and dirty with it.
Categories: Random Commentary
Tags: arch, gnome, kde, linux, lxde, openbox, pacman, vim
5 Comments
osman | February 4, 2010 6:10 PM
Good article. I have been using ubuntu for a long time but I don't like the its speed. I definitely give a chance to arch linux.
Nucco | February 5, 2010 7:12 AM
Nice write up Dennis. If you interested in other distros without a lot of bloated software that comes bundled with it, slackware and slax are pretty good Linux distros I've heard as well.
TThe only thing about slackware is that takes a modular approach to software/package installation so the selection can be limited, but makes insalling a bit easier.
Nucco | February 5, 2010 7:13 AM
In my above comment, I meant slax, not slackware, uses the modular package design. Slackware is mainly command line (or all if memory serves me).
Michael | February 24, 2010 8:48 AM
If you like the minimalist, "build it from the ground up" approach of Arch - which I do - you may also be interested in Gentoo.
You build an Arch system from scratch by bootstrapping the system and then installing whatever binary packages you like.
You build a Gentoo system likewise, by bootstrapping the system and then installing whatever packages you like. The difference is that the packages are compiled from source rather than installed as binaries.
This has the advantage that Gentoo supports a myriad of processor architectures, not just x86 and x64, and you can configure the compiler to optimise the code for your particular processor architecture.
It also has the disadvantage that, with all that compiling, installation can take a fair time, as you sit back and watch gcc do its thing. The bootstrapping process is also a bit more labour-intensive, and a fair bit more tedious, as it's even more "bare metal" than Arch. Whereas the Arch installation guide is probably a couple of dozen printed pages, the printed Gentoo installation guide is a hundred or more pages.
However, if you like one, you'll quite probably like the other, as they have similar philosophies.
Jema | November 13, 2009 11:24 PM
I quite like Arch. While it can be a little hard to get running, it's a very comfortable experience from there on.
I'm still, for the most part, a Fedora user though.