public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Solar Designer <solar@openwall.com>
Cc: Willy Tarreau <wtarreau@hera.kernel.org>,
	linux-kernel@vger.kernel.org, mtosatti@redhat.com,
	Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Linux 2.4.34-pre1
Date: Sat, 19 Aug 2006 01:11:15 +0200	[thread overview]
Message-ID: <20060818231115.GC7813@stusta.de> (raw)
In-Reply-To: <20060818224814.GA10524@openwall.com>

On Sat, Aug 19, 2006 at 02:48:14AM +0400, Solar Designer wrote:
> Hi Willy,
> 
> On Wed, Aug 16, 2006 at 10:36:33PM +0000, Willy Tarreau wrote:
> > Also, I've been asked by several people to consider merging Mikael
> > Pettersson's gcc4 patches :
> > 
> >    http://user.it.uu.se/~mikpe/linux/patches/2.4/
> > 
> > I've been reluctant at first for the usual reasons : "who has a 2.4
> > distro with gcc4 ?" ...
> 
> We're about to migrate Openwall GNU/*/Linux (Owl) from its current gcc
> 3.4.5 (which we used in our 2.0 release) to gcc 4+ - and we'd rather
> _not_ migrate to Linux 2.6 at the same time, if we can.  We'd be more
> comfortable migrating to Linux 2.6 a few months later.
>...

Considering that it's really easy to compile the kernel with a different 
compiler than the userland, do you _really_ want to use such a 
relatively untested kernel/gcc combination for a server platform?

cu
Adrian

-- 

    Gentoo kernels are 42 times more popular than SUSE kernels among
    KLive users  (a service by SUSE contractor Andrea Arcangeli that
    gathers data about kernels from many users worldwide).

       There are three kinds of lies: Lies, Damn Lies, and Statistics.
                                                    Benjamin Disraeli


  reply	other threads:[~2006-08-18 23:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 22:36 Linux 2.4.34-pre1 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
2006-08-17  9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11   ` Adrian Bunk [this message]
2006-08-18 23:27     ` Solar Designer
  -- strict thread matches above, loose matches on Subject: below --
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=20060818231115.GC7813@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mtosatti@redhat.com \
    --cc=solar@openwall.com \
    --cc=wtarreau@hera.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