To view parent comment, click here.
To read all comments associated with this story, please click here.
Maybe it is if you're comparing it to doing everything in a GUI, but the rc.conf system is *simple* compared to most SysV init systems, it's one of the reasons for Arch Linux's popularity. (Amongst people who don't want the limitations of GUI configuration systems, at least.) Compare it instead to configuring Debian or Red Hat without X, and you'll see that its actually quite simple. (Though Debian through debconf and Debian-specific utilities hides some of this.)
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.








Member since:
2005-07-06
Indeed, setting rc.conf and locales is a pain in the ass.