gmane.linux.openwall.user

Owl and 2.6 kernel

Hi together,

I had to exchange several machines with newer hardware and now I have to
use a newer kernel (2.6.25) because of the unsupported ICH9 chipset in
2.4.35.

Are there any roadmaps/timetables to switch Owl to an 2.6 Kernel, or do
I have to use an unpatched kernel for my new hardware?

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

Any experiences?

Greetings
Bernhard

--

-- 
To unsubscribe, e-mail owl-users-unsubscribe <at> lists.openwall.com and reply
to the automated confirmation request that will be sent to you.

headers

gremlin | 25 Apr 09:10

Re: Owl and 2.6 kernel

On Fri, Apr 25, 2008 at 08:02:45AM +0200, Bernhard Fischer wrote:
 > I had to exchange several machines with newer hardware and
 > now I have to use a newer kernel (2.6.25) because of the
 > unsupported ICH9 chipset in 2.4.35.
 > Are there any roadmaps/timetables to switch Owl to an 2.6
 > Kernel, or do I have to use an unpatched kernel for my new
 > hardware?

Try building 2.6.24.5 with grsecurity.org's patches (most of them
are not really needed, but some are really good).

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

None I'm aware of.

 > Any experiences?

I use Owl with 2.6 kernels for over 3 years and have no problem
with that.

-- 
Alexey V. Vissarionov aka Gremlin from Kremlin
<gremlin ПРИ gremlin ТЧК ru>

--

-- 
To unsubscribe, e-mail owl-users-unsubscribe <at> lists.openwall.com and reply
to the automated confirmation request that will be sent to you.

(Continue reading)

headers

Solar Designer | 26 Apr 16:01

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

(Continue reading)