Language Selection

English French German Italian Portuguese Spanish

Fallen Under the Spell of Arch Voodoo

Filed under
Linux
Reviews
-s

I received an email the other day from a visitor saying how much he enjoyed reading my reviews, but he was a disappointed as it seems tuxmachines had been ignoring his favorite distro. As it was a nice distro and a new version was released three weeks ago, he felt it deserved some attention. So when my new burner arrived, it was the first distro I tested. In fact, I've been using it for a couple of days now and the author of that email was correct when he said it was fast, stable, and up-to-date. I refer to Arch Linux 0.8 Voodoo.

I used the torrent to pull Arch in, and it came in surprisingly fast. At 300KB/s, it was just about the fastest torrent pull I've experienced, at least recently. 561MB arrived in short order and became the distro that tested if my new dvd/cd burner worked. Not 100% sure what to expect, I mkfs.ext3 this old partition I had laying around and booted the install disk.

The first screen that appears offers some helpful information and the available boot options. I didn't think I needed any and just pressed Enter. They system booted with typical linux standard output and brought me to another information screen with instructions for some of the various installation options, such as the logfile, keymap, or setup method. The setup methods are Normal or Expert. If one chooses the Normal install, they start a setup routine very similar to what is found with Slackware.

The installer for Arch and Slackware are what I refer to as ascii-graphical. I just made up that term years ago to distinguish the ncurses interface from actual text-installs. To this day some folks still call these Slack derived installers "text." Text is just that, text. It's where one must type in every command to accomplish the install. The installer in Slackware, Arch, and Zenwalk, etc, is not text. It might be keyboard driven, but one is offered choices and after navigation with the arrow keys, one clicks OK using the Enter key instead of clicking with the mouse.

After the welcome screen, one chooses the install source. Your choices are from cdrom or ftp. I had downloaded the install iso, so I chose cdrom. One can get a boot image and install over the net from an ftp repository if they prefer. Then one is taken to the setup menu, again similar to Slack's. Here one can prepare their harddrive using cfdisk or allow the Arch install program to auto-prepare the disk. This latter method takes over the whole drive and makes the necessary partitions. If one doesn't need to make partitions, they can skip ahead to selecting the swap and / partitions and choosing the filesystem. One can choose their favorite filesystem from reiserfs, ext2 & 3, jfs, xfs, and vfat (iirc).

Next one selects the packages for installation. One screen suggested that one only install the base system first and then install the rest after making sure the base boots. Or that's how I understood it, and that's what I did. I selected base install and Yes to all packages by default. It took no time for this step to finish and I went on to number 4 in the menu, Configure System.

During the first phase of Configure System, one can opt to have their hardware auto-detected. This is always a good idea and when presented with the choice, I always go with auto-detection. This step includes answering some preference questions concerning support for USB devices, firewire, pcmcia, nfs shares, raid, lvm volumes, or encrpted volumes. Then one is asked which is their preferred text editor, vim or nano, so that they can edit the system configuration files.

Editing the system configuration files is not as complicated as it sounds. During this step, one is presented a list of files for review. For the most part, they are already configured. One just needs to glance over them to make sure no changes are in order. For example in /etc/rc.conf you might want to input your hostname, change the timezone, or set your internet connection information. Next is /etc/hosts. In that one you might want to put your ip and hostname.domainname hostname. /etc/fstab will already be set up for your current system, but you can add any partitions you might wish mounted at boot. The /etc/mkinitcpio.conf sounds a bit scary, but it's pretty much ready. I added support for my chosen filesystem, but it might not have been needed. /etc/modprobe.conf is available if you have any exotic hardware. For the most part, this isn't need as most is auto-detected. You will probably want to add your nameservers to the /etc/resolv.conf file. /etc/locales.gen offers a lot of examples and lists of locales, so it's not difficult to pick out yours. And finally there is the root password. This is the interactive portion where one inputs their chosen root password as found in Slack's installer or issuing passwd at the commandline. So, all in all, there really isn't much to do during System Configuration, but one should not skip it.

Next one installs the kernel and bootloader. Again menu-driven one just chooses their preferences. Grub and lilo are both available. At this point the install is finished and I rebooted into my base Arch install.

At that time I had no X nor window manager. Arch uses pacman for the package manager and it functions in much the same way as apt-get in Debian and derivatives. In fact, the steps are almost identical. One must set up a configuration file of repositories and update the database before using it. As with most distros these days, Arch's pacman.conf already has sufficient repositories configured. You can add your own or uncomment some of the extra choices such as unstable or community. One then updates, or refreshes as pacman calls it, the database with pacman --sync --refresh. It is recommended that we then update the system to current and even after just three weeks there were several updates available for me. I accomplished that with pacman --sync --sysupgrade. There are several handy options to use with pacman, but for the most part, one will only need to issue pacman --sync <package name>. Sync pulls packages in from remote ftp mirrors while -add will install local compressed tarballs. See the online wiki for more options or man pacman is complete as well.

So, in my case I merely typed pacman --sync xorg kde. It took a while to download the 300+MB of packages and with so many, I was a bit nervous that installing them might fail. However, it did not. After downloading for a couple hours, the system worked away for a bit installing packages. A progress bar for each package was displayed to let me know things were proceeding along. And finally it was done. There was no /etc/X11/xorg.conf file present, so I issued the xorgconfig command. It's the same procedure as the old xfree86config. It is an interactive X setup. If you've ever configured or paid attention when accepting the defaults in any Linux install, this configuration shouldn't be much of a problem. Choices are offered and many times only hitting the enter key is required to use the defaults. All one really needs to know is their video card. Knowing the horizonal sync and vertical refresh is quite helpful, but if you don't just pick one of the lower safe choices.

Pacman reported that there wasn't a kdm or xdm available, so I just use xinit /opt/kde/bin/startkde to start KDE. Gnome and XFCE4 are also available. Installing kde pulled in a lot of dependencies (including gtk, *sql libs, cups, lm_sensors, cairo, media codecs, etc) so that with just xorg and kde, I had a complete system ready for use already. After starting KDE, I installed The Gimp and Firefox. OpenOffice.org, koffice, and abiword are also in pacman repos. The KDE version is 3.5.6, the kernel is 2.6.20, gcc is 4.1.2, gimp is 2.2.13, firefox is 2.2.0.3, gnome is 2.18, and xfce4 is 4.4.1. A full list of current and extra, as well as testing and unstable, packages can be found here.

In the KDE desktop, one finds the complete KDE suite. It's mostly default, but Arch has added their own customized wallpaper and splash screen. It a really pretty blue background with a nice modernistic almost jellied version of the Arch arch in the center with the system identification in the lower right corner. The busy cursor is a teny tiny little blue arch as well. That's pretty cute. In the menu one finds an entry labelled Archlinux that leads one to handy links to the various hotspots on the Arch website, such as Documentation, Forum, Donate, and homepage.

        


I searched the forum for a few answers, such as how to improve the gtk fonts, and I found that the forum is quite active and full of information. It seems from a cursorary glance that all questions are answered in a useful and friendly manner. The Documentation could use a bit more detail in certain areas, but they have a lot more documentation some others. So, all in all, it's quite useful.

This release marks the end of an era for Arch. Beginning with the next release, there will no longer be the .7, .8, or 1.0 type version numbers. They state that from now on they will be versioning their releases to coincide with the release date, year and month.

In conclusion I found Arch to be just what it advertises. "Arch is fast, lightweight, flexible and simple." Some say that it may not be newbie friendly, but I tend to disagree somewhat. Sure there's a bit of configuration needed, but nothing that should be overwhelming. Anyone that has installed any Linux before can probably handle installing and configuring Arch.

I think Arch's most significant strong point is in the fact that it's so customizable. Unlike some distros that install everything or offer rigid defaults, one installs just what they need and want with Arch. With the surprisingly complete repos, one can install how little or much software they choose. With the trend in Linux these days of making things so easy for the newcomer, sometimes one loses most of the choices once offered. So, Arch Linux is a refreshing change of pace. What user configurations are needed are not complicated and sane defaults or useful real-world examples are offered for most. All my hardware was auto-detected, so no configuration was needed in that area. My only complaint is I'm going to have to do some more work on the fonts. Whereas the fonts aren't what one might classify as ugly, they aren't as pretty as on some systems. I would also suggest they dress-up KDE a bit more.

Arch Linux Homepage
Arch @ Distrowatch





ArchLinux

One note. Kdm is part of kdebase, it's not a seperate package.
Also, I really recommend you try gnome under ArchLinux as it works much better than kde.
I've been running gnome for over a year and a half on ArchLinux and I am very satisfied with the current gnome 2.18
Here's my current ArchLinux desktop http://img362.imageshack.us/img362/3408/screenshotzp9.png
Finally, thank you for writing this excellent review of ArchLinux.

ArchLinux

I really recommend you try kde under ArchLinux as it works much better than gnome.
I've been running kde for over a year and a half on ArchLinux and I am very satisfied with the current kde 3.5.6

You think so?

I'm running arch since 2004 now, without gnome even installed. I never had any problems with KDE, or any cooponent of it, and think the kde maintainers do a great work on it (working with kde since version 1 or 1.2 of kde, and for me it always made a better impression than gnome).

What gnome differs from kde: not that many apps are installed with gnome. More choice is given, but i like even xfce more than gnome. At least - with arch we have the choice.

The review is pretty much what i feel about arch. There could be done a lot of making it easier for several "special" usage, and in some terms more user friendly (network scripts and similar), but it's a complete and friendly distribution. Personally, i liked the comment about the forum best, since that is what actually makes archlinux to what it is - the communtiy.

Though, i'm developing on the system, and don't "work" in a common way (mail, office, watching movies, playing mp3s, ..). For Office and Mail i use Citrix, which is fully integrated into the linux desktop since version 10.

ArchLinux

bugme, I never said KDE is bad. Both Gnome and KDE are equally good. It's a matter of taste and I just happen to prefer Gnome over KDE.

silly and sad

It's sad that someone would lie when what they wrote is right there in black and white, and silly when it's something so inconsequential as a desktop preference.

Great review

Thanks for the great ArchLinux review. We currently have a little list going on the main archlinux.org page of reviews of the distro - would you mind if we linked here?

re: Great review

Naw, I don't mind at all. Thanks. Congrats on a fine release too.

Arch Linux on laptops

Arch Linux seems to be a great distribution for laptops as well. CPU frequency scaling as well as suspend to disk and RAM work with minimal effort when following their wiki. I have been using Arch Linux for several months now without any serious issues and I really love the fact that I can do an entire system upgrade periodically without too much trouble and without having to burn new CDs. Also, I was able to install the earlier version of Arch Linux with LVM using the command line even though I am a relative newcomer to using Linux. Apart from this Arch Linux also offers the option to install packages from source if necessary! Indeed a great distribution!

re: arch on laptops

That is wonderful news. Thanks so much for sharing. I felt a little bad I didn't test it on my laptop, but I knew basic support was there. I saw some of the packages being pulled in for the KDE install.

thanks again.

Arch on laptops

By the way, I forgot to mention that I am using the 64 bit flavor of Arch Linux on my laptop and it works beautifully! For those that may not be already aware, Arch also offers a 64 bit version. Among the hundreds of Linux distributions listed on Distrowatch, there are very few distributions that offer 64 bit support. Given how involved it is to get Gentoo Linux set up and running, Arch is an ideal compromise between binary and source based distribution and a real breeze to keep up to date.

Excellent review about an excellent distro!

Yeah it's me the grandmaster of offtopic blabbering from #PCLinuxOS Wink
I've been using the latest Arch now for some weeks and IMO it truly shines
as a distro for us not so newbie users ... I was waiting for you
to review it and my waiting was worth it thank you srlinuxx Smile

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Okular PDF digital signature improvements coming "soon" thanks to NLnet

Starting on January I will be working on a project named "Improve Okular digital signature support" that has received a grant from the NLnet foundation as part of the NGI Assure fund. This will allow me to work part time on Okular (in case it's not clear I work on Okular on a "when I have time-hobby" basis right now), the planned improvements are: 1. Support for signing unsigned signatures. I know it sounds confusing, think about it like something like the old "sign here" boxes on printed paper forms. Read more

FPGA SoC modules gain networking carrier and new PolarFire SoC model

Enclustra’s “Mercury+ PE3” carrier for its FPGA/SoC Mercury/Mercury+ modules can act as an SBC or plug into a PC via PCIe x8. It offers QSFP+, 4x SFP+, FireFly, and 2x GbE. We also examine a new “Mercury+ MP1” module based on the RISC-V based PolarFire SoC. In May, Switzerland based Enclustra announced a Mercury+ ST1 baseboard for its FPGA/SoC powered Mercury and Mercury+ compute modules. These include a Xilinx Zynq UltraScale+ MPSoC based Mercury+ XU6 module that was announced at the same time. Now the company has unveiled a more feature-rich Mercury+ PE3 board for the Mercury/Mercury+ product line. Farther below, we report on a similarly “in development” Mercury+ MP1 module based on Microchip’s based PolarFire SoC, which includes RISC-V based CPU cores and Microchip’s PolarFire FPGA. Read more

IBM/Red Hat/Fedora Leftovers

  • IBM applauds Knative’s application to join the Cloud Native Computing Foundation

    Today, Knative applied to become an incubating project at the Cloud Native Computing Foundation. Today’s news is a major step in the right direction for the future of Knative. Knative adds the necessary components that enable Kubernetes users to more quickly deploy and manage their workloads on Kubernetes — but without the need to become Kubernetes experts. Additionally, Knative adds “serverless” runtime semantics, allowing users to reap the benefit of features such as quick load-based scaling and scaling to zero when idle.

  • 3 ways to optimize Ansible Automation Platform for scale and performance | Enable Sysadmin

    Try these settings to optimize performance with Ansible Automation Platform on a massive scale.

  • Introduction to Ansible prompts and runtime variables

    This tutorial is part of a series we dedicated to Ansible. Previously we talked about the Ansible basics, then we focused on some Ansible modules we can use to perform some very common administration tasks, and we also talked about Ansible loops. In this article, instead, we learn how to create interactive prompts we can use to ask for user input and how to pass variables at runtime.

  • MIXAL on Fedora | Adam Young’s Web Log

    The examples in The Art of Computer Programming (TAOCP) are in the MIXAL programming language. In order to see these examples run, I want to install the tools on my Fedora box. They are packaged as RPMS, so this is trivial. Here are the steps to run and debug a sample program in MIXAL.

  • Fedora Contributor Annual Survey Data Set Available – Fedora Community Blog

    Over the summer of 2021, the Fedora Council held the first annual Contributor Survey. The survey received 800 complete responses, which exceeded the goal of 500. We have processed the data, which are available for download. Coordination of the survey was a wonderful community effort. Fedora Council member Aleksandra Fedorova proposed and led the survey effort with support from Marie Nordin (FCAIC). Many teams across the Fedora Project contributed, including: the Mindshare Committee, the Outreach Revamp Team, the Design Team, the Websites & Apps Team, and the Community Platform Engineering Team. Aleksandra and Marie presented a session at Nest with Fedora which goes further into the process and outcomes. Over the last couple months, the work of cleaning up the dataset has been underway. This has been a slow process as there are just a couple of people working on that regularly. An example of “cleaning” would be folks who chose “Other”, filled in “idk”, when the option “I don’t know” existed. Those answers need to be integrated in order to have a more accurate dataset. We removed fill-in answers due to the fact that some people identified themselves, intentionally or not. As we process the data, we are noting feedback to improve the survey for 2022.

WordPress 5.9 Beta 1

WordPress 5.9 Beta 1 is now available for testing! This version of the WordPress software is under development. You don’t want to run this version on a production site. Instead, it is recommended that you run this on a test site. This will allow you to test out the new version. Read more Also: People of WordPress: Devin Maeztri