> though. Debian stable is out of date by my standards, and I do not like
> limiting myself to its contents.
<IMHO>
The debian philosophy is "Will release the new distro if it's ready"
just like the Linux kernel. The downside is yes, it's a bit outdated,
but *every* (near 4000+ worth of packages.) software of it will simply
work out of the box, and bugs in the distro squashed.
Take for example new security packages of debian in response to say,
apache security problems. Say, Debian 2.2 has apache 1.3.14. What the
developers usually do is release apache 1.3.14 with security
enhancements! not a new apache 1.3.20 which is say, a newer one.
This is to ensure maximum compatibilty with existing software
dependent on apache and protection from potential bugs that a new
apache release might introduce.
Debian developers strives for quality and stability above else.
> So I use packages from Debian's unstable
> and some unofficial sources (for courier, in particular).
Your inviting trouble. Mixing stable and unstable debian releases
will have give you a problem later on.
If you really want to have the latest whizbang software, you
could:
- compile the software from source and run it from /usr/local.
- compile the software from source and convert to .debs.
(That's why you have unofficial .debs all over the place.)
> I have two crippled Debian boxes. Gusi, my file server,
> cannot compile anything using gcc
Your installing *new* software on production machines that you
depend on? that's insane! your inviting trouble again! just a
tip, doing that stunt on a medium/large company will get you
fired :) go get yourself a development machine to play around
with... say your laptop.
> Stable is stable, but it's too stale for me.
I'm not stating the obvious but... If you want to compile software and
install it for Debian stable, then do it on a seperate machine and test
it there. Not on your production machine. If you have a problem, debian
has a lot of mailing lists to get help. If it's okay, then you have
a choice to installing it to your production machine if it's really
needed.
> Unstable is okay most of the time, but there's no guarantee it won't
> f*ck up on you, and with Gusi I can't take chances.
I think your confusing the roles of what a stable and unstable branch
of debian is.
The stable branch strives to be of high quality software. suitable for
a production server, etc. If you want to introduce new software, test
it beforehand before deploying.
The unstable branch is where newest software are introduced and tested
to be eventually released as the next Debian GNU/Linux. Installing
unstable and using it as a production server is insane. As you have
mentioned, there's no guarantee.
But if you simply want to test new software/Linux kernel (which is i think
what you want.) to play with, then the Debian unstable branch is for you.
I've been doing that for 2 years, and the software of unstable is really
new compared to the other distros. you're talking of new software every
day!
> So like the teenager that I really am anyway, I'm in search of a new
> distribution to test.
Then try Mandrake 8. It has this apt-ish software, distro that takes
security seriously and bleeding edge software/kernel.
> In particular I'm sensitive with distributions that have a
> flaky upgrade system.
Then try Debian. :) I have a server which started with 1.3. I then
upgraded it to 2.0, 2.1 and then to 2.2. That's how good the upgrade
path is.
Your comment that the software of debian is outdated is being
worked out by the developers. Hopefully, they will have a good
solution for this.
As an alternative distro, use "Slackware, I like" :)
I actively use the 3 linux distro (Slackware, Debian, Mandrake),
for a specific use. Hopefully, you may finally find a good distro
that you like.
</IMHO>
regards,
-----
Andre M. Varon <[EMAIL PROTECTED]>
http://andre.lasaltech.com
Fear can hold you prisoner, Hope can set you free.
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
