From: Solar Designer <solar@openwall.com>
To: Adrian Bunk <bunk@stusta.de>
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 03:27:58 +0400 [thread overview]
Message-ID: <20060818232758.GA10886@openwall.com> (raw)
In-Reply-To: <20060818231115.GC7813@stusta.de>
> On Sat, Aug 19, 2006 at 02:48:14AM +0400, Solar Designer wrote:
> > 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.
On Sat, Aug 19, 2006 at 01:11:15AM +0200, Adrian Bunk wrote:
> Considering that it's really easy to compile the kernel with a different
> compiler than the userland,
We want our end users to be able to rebuild all of Owl (including the
kernel) from source using only tools that are a part of Owl, yet we do
not want to be providing multiple versions of gcc (or of any other
package, for that matter). We've been successful at not providing
multiple versions of development tools and libraries so far - keeping
the system small and clean, yet fully self-rebuildable.
> do you _really_ want to use such a
> relatively untested kernel/gcc combination for a server platform?
I expect that we will fully move to Linux 2.6 before our next release,
but being able to move to gcc 4+ in Owl-current first simplifies our
development process. (And, yes, we've got end users of Owl-current who
will be recompiling kernels.)
Also, I expect this kernel/gcc combination to receive quite some testing
soon, if/once it becomes supported.
Alexander
next prev parent reply other threads:[~2006-08-18 23:32 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
2006-08-18 23:27 ` Solar Designer [this message]
-- 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=20060818232758.GA10886@openwall.com \
--to=solar@openwall.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mtosatti@redhat.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