public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Yuhong Bao <yuhongbao_386@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.37.10 + 2.4 EOL plans
Date: Wed, 15 Sep 2010 06:52:22 +0200	[thread overview]
Message-ID: <20100915045222.GA20654@1wt.eu> (raw)
In-Reply-To: <SNT125-W58FE492CE393C28E2D5249C3780@phx.gbl>

On Tue, Sep 14, 2010 at 03:19:54PM -0700, Yuhong Bao wrote:
> 
> OK, I will bite.
> Why are you still using kernel 2.4?

One word : stability.

Many people don't need all the fancy new features of 2.6 and can't afford
to reboot their systems every two weeks to apply the last bunch of fixes.
It's quite common to encounter 2.4 systems with 2 years of uptime in
production. Some users even ship it in embedded products where it's
impossible to update the system after it's shipped (no internet connectivity).
With 2.4, they're assured they won't encounter stability problems.

Some other users still use it for security reasons. 2.6 offers a wider
attack vector range and in practice, new locally exploitable vulnerabilities
are discovered every few weeks-months. I'm not saying that there aren't on
2.4, but since the code is frozen, it's been long since we last got one and
there's no reason to introduce new ones.

In fact, 2.4 is now occupying a similar place as OpenBSD : the type of
system you install once and never touch anymore.

Regards,
Willy


      parent reply	other threads:[~2010-09-15  4:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06  5:45 Linux 2.4.37.10 + 2.4 EOL plans Willy Tarreau
     [not found] ` <SNT125-W58FE492CE393C28E2D5249C3780@phx.gbl>
2010-09-15  4:52   ` Willy Tarreau [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=20100915045222.GA20654@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuhongbao_386@hotmail.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