Linked by Eugenia Loli-Queru on Sat 31st Mar 2007 21:55 UTC, submitted by Kuat
Arch Linux team has just released their Voodoo (version 0.8) ISOs. Many changes and brand new software application versions included, while at the same time the Arch team released Pacman, v3.0, currently available in the -Testing tree.
Thread beginning with comment 226274
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-08
I assume that with Arch Linux, you get a very basic setup, and its up to the installee to configure it to suite his or her tastes - correct?
That's what most people do, it does have a CD with more stuff on it, I forget what that includes, you can check their website to find out. ;-) One doesn't rely on releases either, it is a "rolling release", the installer only gets updated due to infrastructure needs.
It sort of reminds me of a cross between Slackware (simple init and configuration), Debian (package management), and a drop of Gentoo (abs) if you want that. A unique feature is AUR, it offers a repository, along with the decent-sized official repositories, that is user-contributed with little approval process; which means it has lots of packages without the package-approval-bureaucracy. Of course, that means its wise to examine the package builds of AUR stuff before you install if it hasn't received approval yet.
Member since:
2005-07-06
I assume that with Arch Linux, you get a very basic setup, and its up to the installee to configure it to suite his or her tastes - correct?
Alot of the speed issues that come with Red Hat/Fedora and OpenSuSE are due to the fact that it tries to be everything to everyone, the net result, for example, you have hardware detection things that load at start up which slow things down etc.
I might give it ago, however, I think I might wait till the new driver for ipw3945 is released, which no longer relies on the userland demon, that can be a real bitch to setup, making sure that it is loaded before the wpa_supplicant, but ensuring there is a sufficient 'gap' in the load proceedure or otherwise, wpa won't work - and ontop of all that, making sure thare all that occurs before the ethernet connection is initialised.