On Wed, Jan 05, 2011 at 07:19:18AM -0500, lanas wrote:
> I'd like to thank Fons for mentionning ArchLinux. I used to build my
True, with the advantge that you get up-to-date binary install packages
for most things you'll need, and don't *have* to compile everything.
And even if it is a rolling release it is perfectly possible to create
a long-term stable system using ArchLinux. I manage some machines which
are *not* updated regularly - they are dedicated to a particular function,
and just don't require the latest and greatest.
The only trouble you can have with such systems is when after a year or
so you want to install something completely new. More often than not the
new package will depend on recent releases of libraries etc. This can
trigger a dependency explosion that usually leaves you with the single
realistic option of doing a complete system upgrade which after a year
will replace almost everything. That in turn may require some manual
tweaking afterwards if some fundamental things have changed. So just
don't do this on impulse but be prepared for it.
It's also easy to 'lock' certain things, e.g. the kernel or X11 if you
expect problems with the new ones. But the most important thing for a
system update is to plan it: don't do it if you need the machine the
next hour. I got some unpleasant surprise only once when a system update
replaced 'nv' with 'nouveau' - the former is an X11 driver while the
latter is a kernel module. Not being aware of that, I botched up the
complete X11 configuration. But even that was repaired within an hour
or two, the time to find and read the necessary documentation on the
Arch Wiki. A second machine for web browsing is a good thing to have.
There are three of them, and Alleline.
Linux-audio-user mailing list