mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Adrian Bunk <bunk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 usage statistics
Date: Tue, 29 Apr 2008 21:06:32 +0200	[thread overview]
Message-ID: <481771B8.9070105@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080428211812.GA19093@1wt.eu>

Willy Tarreau wrote:
> Speaking for my case, at Exosec we still use 2.4 a lot. Main reason is that
> we are used to apply a lot of patches. [...]  I have already thought about
> moving to 2.6.16, but I would have had to port my patches, [...]
> Since I would have gained nothing in this operation, it
> was easier to stick to 2.4.
> 
> I'm waiting for other people's excuses now :-)

A variation of the theme, which I as maintainer of some drivers in 2.6 
heard by way of occasional questions on subsystem mailinglists or 
off-list:  Kernel customizations for embedded systems in combination 
with a custom userland.  Moving all this software over to 2.6 was not 
considered worth the effort.

Another reason which I read here and there and don't know how real the 
issue is:  2.6's minimum possible footprint is said to be unable to 
compete with 2.4 for really resource restricted applications.

Could it actually be that 2.4 outnumbers 2.6 in embedded installations?

(I don't work with 2.4 myself and I don't know the domain of embedded 
systems.)
-- 
Stefan Richter
-=====-==--- -=-- ===-=
http://arcgraph.de/sr/

  reply	other threads:[~2008-04-29 19:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 20:24 Willy Tarreau
2008-04-28 20:56 ` Adrian Bunk
2008-04-28 21:18   ` Willy Tarreau
2008-04-29 19:06     ` Stefan Richter [this message]
2008-05-04  1:01       ` Lee Revell
2008-05-04  8:45     ` Jean Delvare
2008-06-01 23:50 ` Linux 2.4 usage statistics (results) Willy Tarreau

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=481771B8.9070105@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®