Arch In Depth
The LinuxTimes Editor wrote in to alert us to a LinuxTimes article entitled Arch In-Depth, discussing the Arch Distribution. From the article: "First of all, let me go ahead and say I'm not approaching Arch with a completely clean slate. I've heard things about Arch Linux before. I've heard that it resembles Slackware in the way it was lean and meant for "advanced users". I've heard about its package manager called Pacman which is supposed to be all the rage. I've heard it's optimized for i686 by default which can arguably improve performance. I've heard it's Gentoo without "all that compiling". So when Arch 0.7 got out a few days ago I simply had to try it out."
OK, so much for this reviewer.
OK, so much for Arch. (Turns out you have to pacman gnome-extra to get everything.)
Turns out that Arch is extremely minimalist; you get only what you asked for and sometimes less than you asked for. This is probably good for, say, embedded systems, but for most of us with our 100GB+, 200GB+, drives, there's not a whole lot of point to leaving things out. Though there are people who will be quite happy with this.
I'm not one of them.
I wouldn't be surprised at all if every Slackware user dropped Slack and went to Arch. It sounds like a much better Slackware than Slackware. But, again, this approach is not for me. Ironically, my favorite distributions are Gentoo and Fedora (in that order). Yes, I'm weird.
How am I supposed to fit a pithy, relevant quote into 120 characters?
Bitmaps? Bitmap images? You voluntarily submitted an article to Slashdot that uses bitmap images? Every single image on that site is 800KB . Or more!
And no, they didn't use actual thumbnails for the images, they link these monstrous images and resize them with HTML.
I don't just not trust the reviewer, I don't trust the site! That is some seriously stunning incompetence for a website.
(Of course, this will either be fixed, or you later "readers" won't be able to get through to the hammered server.)
If you really want to read this and you are on dial-up, don't bother loading the images, they're just "screenshots" of console applications (yes, that's right, 2000 chars of text and some color information; we're talking an image that even with a really crappy 'bitmap' style encoding of the text would only have 4000 bytes was blown up to over a megabyte in some cases), that typically have almost no useful information anyhow.
I, for one, applaud that another distro has the balls to enter what is increasingly a saturated market for minimalist distros. There must be two dozen micro-distros for really tiny embedded/small-footprint apps and about the same number of the next-larger variety, which seems to be the target niche of this system.
So, why do I applaud yet another entry in this gladiatorial matinee? Because it seems to be (as others have already mentioned) gentooish without being gentoo. As much as I love the ideology behind gentoo, it is a little self-defeating in the (ironically) places where it was meant to be most effective: weak systems. If you've ever tried compiling from a stage 1 on a pentium-133, you will know what I mean. Between the copying, set-up, compiling and post-config, it easily becomes a week-long install. (Well, if you only attend to it post-commute, that is.)
Given that the only people who actually still use P-133s for anything are (usually impatient) techies hacking out a sideproject, it's nice to see yet another distro enter the competition and allow us to make another choice without needing to postpone the project by yet another week for testing.
And yes, the review sucks.
I doubt that those precompiled 686 binaries would appeal much to Gentoo users with AMD64, PowerPC, UltraSparc, Alpha and MIPS systems.
And as for "all that compiling", Gentoo allows you to install from binary packages if you must. But I compile away some of the bloat via USE flags; you can't do that with Arch binaries.
I use Ubuntu as a stable base and chroot into Gentoo to run other stuff.
/mnt/gentoo /bin/change-to-gentoo-and-bash)
...maybe.
I haven't scripted it yet but will do soon
(chroot
I may check out this distro to replace Ubuntu
A blog I run for the wealth
It's called "etc-update". It goes with Gentoo's (apparent) philosophy of forcing the user to manually go through some post-installation steps such as updating config files and restarting services, after everything is done. Unfortunately, there's no really good way to tell it to restart all services which have just been updated.
I would argue that etc-update is significantly easier than debconf, but maybe that's because I don't know vimdiff at all.
Don't thank God, thank a doctor!