linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 -> 2.2 differences?
Date: Fri, 25 Jul 2003 15:34:20 -0700	[thread overview]
Message-ID: <20030725223420.GD25838@pegasys.ws> (raw)
In-Reply-To: <20030725142434.GS32585@rdlg.net>

On Fri, Jul 25, 2003 at 10:24:34AM -0400, Robert L. Harris wrote:
> 
> 
> With all the SCO fun going on I have people asking me what functionality
> we would loose if we rolled from 2.4.21 kernel to the last known stable
> 2.2 kernel.
> 
> Yes, weathering the lawsuit mess and all is a good plan but I'm still
> being asked for this information.  Does anyone have a link listing what
>  kind of functionality would be lost, performance impact (p3 and athalon
> machines), etc?

You could start with Joe Pranevich's "Wonderful World of
Linux 2.4" at
http://linuxtoday.com/news_story.php3?ltsn=1999-10-03-001-05-NW-LF

There have been a number of improvements and features added
since but any 2.2 -> 2.4 features summary should indicate
much of what you would loose in a 2.4 -> 2.2 transition.



-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  parent reply	other threads:[~2003-07-25 22:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 14:24 2.4 -> 2.2 differences? Robert L. Harris
2003-07-25 18:08 ` Mike Fedyk
2003-07-25 22:34 ` jw schultz [this message]
2003-07-25 23:29 ` Bernd Eckenfels
2003-07-26  0:02   ` Alan Cox
2003-07-26  0:47     ` Robert L. Harris
2003-07-26 12:36       ` Alan Cox
2003-07-26 22:49         ` Robert L. Harris
2003-07-26 15:25     ` Geert Uytterhoeven
2003-07-28 15:00   ` Robert L. Harris
2003-07-31 19:32 ` Andrew Scott

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=20030725223420.GD25838@pegasys.ws \
    --to=jw@pegasys.ws \
    --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;
as well as URLs for NNTP newsgroup(s).