mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>,
	linux-kernel@vger.kernel.org, mtosatti@redhat.com,
	Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Linux 2.4.34-pre1
Date: Thu, 17 Aug 2006 10:37:02 +0200	[thread overview]
Message-ID: <20060817083702.GB14673@1wt.eu> (raw)
In-Reply-To: <1155797331.4494.17.camel@laptopd505.fenrus.org>

Hi Arjan,

On Thu, Aug 17, 2006 at 08:48:51AM +0200, Arjan van de Ven wrote:
> 
> > Right now, I'd prefer getting gcc 4 support than gcc 3.4, because I don't
> > know if even one common distro has shipped with gcc 3.4 by default. 2.95,
> > 3.0, and 3.3 have been common, and right now, 4.[01] is almost everywhere.
> 
> but most distros that ship with gcc 4 aren't capable of running a 2.4
> kernel.... all the new distros greatly depend on sysfs for example, and
> ntpl in glibc requires 2.6 etc etc etc. So I'm rather sceptical about
> this argument.

I know, and this is not what I'm targetting. People use 2.4 on their file
server or firewall for instance, on an old distro, while they use 2.6 on
their notebook with newer gcc. They build from their fresh new system
(because most often you don't install build tools on a server) and this
is at least why some of them have already been asking for this. To be honnest,
I don't really need gcc 4 myself right now, but I'm more responding to some
users demand that I find somewhat legitimate.

> > >   Since there shouldn't be any reason for still using a 2.4 kernel
> > >   except for "never change a running system",
> > 
> > I think that by "never change", you meant "except for regular updates".
> 
> I think that you'll find that people who run 2.4 today, if you ask them,
> will say "please change as little as possible, only serious bugs and
> security issues". After all the people who run 2.4 still are generally
> those who resist new stuff in favor of stability of existing systems....
> But maybe it's worth doing a user survey to find out what the users of
> 2.4 want... (and with that I mean users of the kernel.org 2.4 kernels,
> people who use enterprise distro kernels don't count for this since
> they'll not go to a newer released 2.4 anyway)

Agreed, that's also why I've left it in another tree right now, so that
interested people can test it and other ones have the time to pronounce
themselves against it if needed. Anyway, as I said, most of the fixes were
for real coding bugs, and do not affect either the output code nor external
patches. I don't want to experiment with new killer features at all, if I
accepted to work on 2.4, this is because I'm rather conservative ;-)

Cheers,
Willy


  parent reply	other threads:[~2006-08-17  8:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 22:36 Willy Tarreau
2006-08-16 23:54 ` Adrian Bunk
2006-08-17  5:16   ` Willy Tarreau
2006-08-17  6:48     ` Arjan van de Ven
2006-08-17  8:35       ` Andreas Steinmetz
2006-08-17  8:50         ` Mikael Pettersson
2006-08-17 12:48           ` Adrian Bunk
2006-08-17 20:43             ` Willy Tarreau
2006-08-17 23:41               ` Gerd v. Egidy
2006-08-18  4:40                 ` Willy Tarreau
2006-08-21  0:56               ` Adrian Bunk
2006-08-17  9:06         ` Adrian Bunk
2006-08-17  9:16           ` Andreas Steinmetz
2006-08-18 23:25             ` Adrian Bunk
2006-08-19  1:20               ` Grant Coady
2006-08-20 17:27                 ` Adrian Bunk
2006-08-19  4:45               ` Willy Tarreau
2006-08-21  0:35                 ` Adrian Bunk
2006-08-21  0:41                   ` Willy Tarreau
2006-08-21  1:07                     ` Adrian Bunk
2006-08-17  8:37       ` Willy Tarreau [this message]
2006-08-17  9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11   ` Adrian Bunk
2006-08-18 23:27     ` Solar Designer
2006-08-17  7:57 Chris Rankin
2006-08-17  9:16 ` Thomas Backlund
2006-08-18  4:47   ` 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=20060817083702.GB14673@1wt.eu \
    --to=w@1wt.eu \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mtosatti@redhat.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

all inboxes | Powered by JetHome®