From: "A.D.F." <adefacc@tin.it>
To: linux-kernel@vger.kernel.org
Subject: linux-2.2 future?
Date: Fri, 22 Aug 2003 21:27:25 +0000 [thread overview]
Message-ID: <3F468ABD.1EBAD831@tin.it> (raw)
> On Wednesday 20 August 2003 14:3, Ruben Puettman wrote:
>> On Wednesday 20 August 2003 13:59, Marc-Christian Petersen wrote:
>>
>> Hi Alan,
>>
>>> On Wednesday 20 August 2003 13:46, Alan Cox wrote:
>>> he 2.2 tree needs a new maintainer, someone who can spend their entire
>>> life refusing patches, being ignored by the mainstream (because 2.2 is
>>> boring) and by vendors (who don't ship 2.2 any more).
>>
>> I want to take 2.2.
>>
> What's up with linux-2.2 now? Who will do Alan's job in the next year?
>
> Marc is intrested doing this job. I know Marc from linux-2.2.x-secure
> and from the wolk project, see http://wolk.sourceforge.net. Why not
> Marc? He can surely differentiate between mainstream and a private kernel fork
> tree. Or do you think, Marc will merge every single bit out of his kernel tree
> into mainstream? I bet he won't
>
> I can't see postings from other people who want to take 2.2.
>
> I think 2.2 is not dead. I often see 2.2 kernels running on systems like
> wlan access points or dsl routers from different vendors. 2.2 is often
> used where stability is a must-have. At least security fixes have to go in.
I agree.
> What do you think?
Well, I think that 2.2.24 and 2.2.25 kernels are really stable (at least on
UP), but that the most weak side is on IDE disk drivers.
They seem to have DMA problems when using recent hard disks (i.e. Maxtor,
etc.)
that lead to serious file system corruption problems.
Maybe there are also geometry problems because all troubles have been
observed
on disks with more than 32 GB of capacity (i.e. 40 GB).
This is a pity because, up to now, 2.2.x kernels have been
a valid choice for small / semi-embedded systems 80x86
(yes, I know that 2.4 should be better, but I'm still waiting for
a stable rock kernel).
In conclusion, I hope that next maintainer will think about
these matters:
IDE drivers;
security fixes;
micro-optimizations;
compatibility with newer compilers.
After all if 2.0 seems to be still alive also 2.2 should be.
A. De Faccio
next reply other threads:[~2003-08-22 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 21:27 A.D.F. [this message]
2003-08-25 16:42 ` linux-2.2 future? Marc-Christian Petersen
2003-08-26 15:03 ` Alan Cox
2003-08-27 22:27 ` Neale Banks
2003-08-27 22:40 ` Marc-Christian Petersen
[not found] <mzDG.3ry.27@gated-at.bofh.it>
[not found] ` <mzWX.3MH.5@gated-at.bofh.it>
[not found] ` <mV1t.7Wj.15@gated-at.bofh.it>
2003-08-22 11:22 ` Ruben Puettmann
2003-08-22 17:46 ` Mike Fedyk
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=3F468ABD.1EBAD831@tin.it \
--to=adefacc@tin.it \
--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