From: Kenneth Scharf [mailto:firstname.lastname@example.org]
Sent: Monday, May 01, 2000 11:53 AM
Subject: Re: potato late, goals for woody (IMHO)
The point is I HAD to get potato even though it was
not yet "stable" if I wanted to use some of the newer
stuff. (libc2.1). Not that I prefer to live on the
bleeding edge (if I did I would be running slackware).
>Slink is so old now as to be borderline useless.
>With its basis of
>2.0 instead of 2.1, slink will not run the Sun JDK
>and all sorts of other things we need. As a result,
>we actually have
>production web servers and database servers running
>on potato, which is
>not technically stable. We regard this as extremely
Actually Potato doesn't seem to be unstable at all. I usually take frozen to mean that the code is pretty much ready for release. I've got it working on a prototype laptop with questionable hardware all over, and the base system works beautifully. I had to do a bunch of tweaks to X, and sound still doesn't work right, nor do APM utils (APM itself works great), but battery meter apps don't.
Potato is basically (although many will argue) stable now. Debian developers just like to be really sure it works right before they brand it as such.
Epitaph for Bill Gates: "This man performed an illegal operation and was shut down" --BBC
SGI and Motorola team up to design a new chip... the Crayola --personal
Apple MacOS X the only UNIX where dumping cores is a good thing. --personal
Bastille Linux - You have to run your servers in headless mode.
Curses! Curses! Scrolled Again!