Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080426140146.GA11923@openwall.com>
Date: Sat, 26 Apr 2008 18:01:46 +0400
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: Owl and 2.6 kernel

On Fri, Apr 25, 2008 at 08:02:45AM +0200, Bernhard Fischer wrote:
> Are there any roadmaps/timetables to switch Owl to an 2.6 Kernel,

We wanted to do it before the next release, but right now it seems more
likely that the next release will be the last one to use a 2.4 kernel -
that is, that we'd switch to 2.6 after the next release.  We are also
very likely to integrate OpenVZ.

> or do I have to use an unpatched kernel for my new hardware?

Yes, if your hardware is unsupported by 2.4 kernels, you'll have to use
a 2.6 kernel without our patches.  We're often using the OpenVZ kernels
from OpenVZ's "RHEL5" branch.  They work fine with the Owl userland,
which we use both on the host system and inside containers (also known
as VEs or VPSes).

> Which packages are kernel-dependent and should be rebuild under the new
> kernel?

The short answer is: none.

In fact, it is more correct to have your packages built against the same
kernel headers that glibc was built against.  So if you don't rebuild
glibc (and there should be no need to do that), it is more correct to
not rebuild any other packages against 2.6 kernel headers as well.

-- 
Alexander Peslyak <solar at openwall.com>
GPG key ID: 5B341F15  fp: B3FB 63F4 D7A3 BCCC 6F6E  FC55 A2FC 027C 5B34 1F15
http://www.openwall.com - bringing security into open computing environments

-- 
To unsubscribe, e-mail owl-users-unsubscribe@...ts.openwall.com and reply
to the automated confirmation request that will be sent to you.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.