From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.22 released
Date: 28 Aug 2003 02:31:04 GMT [thread overview]
Message-ID: <bijph8$pqq$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 200308270610.h7R6Ajwt000277@81-2-122-30.bradfords.org.uk
In article <200308270610.h7R6Ajwt000277@81-2-122-30.bradfords.org.uk>,
John Bradford <john@grabjohn.com> wrote:
| Yes, of course, but the majority of desktop, workstations and server
| machines run whatever kernel their distribution supplies.
|
| Within a year, a lot of distributions will start offering both 2.4 and
| 2.6. The only reason to run the distribution's 2.4 kernel will be if
| the 2.6 one doesn't work on the user's hardware. In that case, we
| will want to add support to/fix 2.6 as a priority, rather than adding
| support to 2.4.
|
The "must have" feature of 2.4 was iptables. You simply can't do as good
a firwall or network device without stateful sockets. Other than device
drivers the kicker of 2.6 is crypto. If you need the features you really
will go.
Latency in 2.4 seems better, at least for some of the stuff I use, and I
see the new scheduler and NPTL are in the latest Redhat 2.4, so those
are not compelling for most people.
I would still like to see all the responsiveness features, VM, low
latency, preempt current. The O(1) scheduler is still getting better
daily in 2.6, about 2.4.25 that should be ready. Then when what we have
is working as well as it can, we can add features.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-08-28 2:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 6:10 linux-2.4.22 released John Bradford
2003-08-28 2:31 ` bill davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-27 11:10 Vid Strpic
2003-08-26 22:25 John Bradford
2003-08-27 2:11 ` Ramón Rey Vicente
2003-08-25 17:20 Mikael Pettersson
2003-08-27 21:45 ` Marc-Christian Petersen
2003-08-25 16:53 Marcelo Tosatti
2003-08-25 16:25 Mikael Pettersson
2003-08-25 16:40 ` Marc-Christian Petersen
2003-08-25 11:48 Marcelo Tosatti
2003-08-25 8:11 ` Enrico Demarin
2003-08-25 13:23 ` Matthias Andree
2003-08-25 13:32 ` Christoph Hellwig
2003-08-25 13:35 ` Ramón Rey Vicente
2003-08-25 21:13 ` J.A. Magallon
2003-08-25 22:22 ` Adrian Bunk
2003-08-26 0:21 ` Ramón Rey Vicente
2003-08-26 21:49 ` Diego Calleja García
2003-08-26 21:55 ` Adrian Bunk
2003-08-26 22:29 ` Diego Calleja García
2003-08-27 2:15 ` Ramón Rey Vicente
2003-08-27 5:21 ` Gerardo Exequiel Pozzi
2003-08-27 1:20 ` Chuck Campbell
2003-08-27 1:48 ` David van Hoose
2003-08-27 1:55 ` David van Hoose
2003-08-27 3:28 ` Kurt Wall
2003-08-27 2:01 ` Ramón Rey Vicente
2003-08-27 4:12 ` Willy Tarreau
2003-08-26 22:29 ` Matthias Andree
2003-08-27 9:47 ` Bas Mevissen
2003-08-26 13:55 ` Matthias Andree
2003-08-25 13:38 ` Nick Piggin
2003-08-25 22:34 ` Bill Davidsen
2003-08-25 14:38 ` Yann Droneaud
2003-08-25 15:35 ` Krzysztof Halasa
2003-08-25 16:03 ` Luca Montecchiani
2003-08-25 19:18 ` Erik Andersen
2003-08-25 20:00 ` Edesio Costa e Silva
2003-08-25 20:10 ` Tom Rini
2003-08-26 13:19 ` Rene Rebe
2003-08-26 15:00 ` Alan Cox
2003-08-27 3:47 ` CaT
2003-08-26 16:11 ` Willy Tarreau
2003-08-26 19:32 ` Greg KH
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='bijph8$pqq$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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