From: John Alvord <jalvo@mbay.net>
To: Riley Williams <rhw@MemAlpha.cx>
Cc: Vinolin <vinolin@nodeinfotech.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Latest stable
Date: Sun, 16 Sep 2001 23:06:15 -0700 [thread overview]
Message-ID: <0e4bqtsqmdcblr60vjl4147pn7qctttvka@4ax.com> (raw)
In-Reply-To: <006c01c13b90$104b8a40$080aa8c0@nodeinfotech.com> <Pine.LNX.4.21.0109160803210.24288-100000@Consulate.UFP.CX>
In-Reply-To: <Pine.LNX.4.21.0109160803210.24288-100000@Consulate.UFP.CX>
On Sun, 16 Sep 2001 08:09:14 +0100 (BST), Riley Williams
<rhw@MemAlpha.cx> wrote:
>Hi Vinolin.
>
>> Can you please reply me "which is the stable version of linux" now?
>
>That depends what you mean by "stable", as there are currently two
>parallel stable development trees:
>
> 1. "Stable and ready for production use" is the latest 2.2 series
> kernel, found at ftp://ftp.kernel.org/pub/linux/kernel/v2.2/ on
> the Internet.
>
> 2. "Stable but untested in production use" is the latest 2.4 series
> kernel, found at ftp://ftp.kernel.org/pub/linux/kernel/v2.4/ on
> the Internet.
It would be most accurate to label 2.4 as "stablizing", meaning that
bug fixes only are being accepted. Of course some pretty extensive
bugs are being working on... like the Virtual Memory area...
Stable versions come from distributors who test a given level
extensively, and add in any needed fixes, and stand behind the result.
You can't expect that from developers and you won't get it even if you
do expect it.
>
>Basically, the 2.4 series kernels are stable and contain all the latest
>kernel technology, but you are advised to test your setup on a system
>whose stability doesn't matter and satisfy yourself that they are
>suitable for your use.
>
>Best wishes from Riley.
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-09-17 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <006c01c13b90$104b8a40$080aa8c0@nodeinfotech.com>
2001-09-16 7:09 ` Latest stable Riley Williams
2001-09-17 6:06 ` John Alvord [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e4bqtsqmdcblr60vjl4147pn7qctttvka@4ax.com \
--to=jalvo@mbay.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.cx \
--cc=vinolin@nodeinfotech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).