[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 28 Jun 2012 00:12:59 +0400
From: Vasily Kulikov <segoon@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: status of 2.6.32-based kernel
(attaches are too big, resending email with ftp links)
On Sun, Jun 24, 2012 at 05:50 +0400, Solar Designer wrote:
> Do you already have an updated kernel.spec?
ftp://ftp.ru.openwall.com/pvt/segoon/pub/kernel.spec
It also needs additional kernel-firmware package or so, now it just
ignores firmware files.
> Have you already tried building the Owl userland with this kernel's
> headers? If so, how many packages build / don't build?
Actually while typing this email I've noticed that I tried to build
world with old headers. I'll post about results tomorrow after full
i686 and x86_64 worlds rebuilds. Sorry :(
> > 1. Owl patch is updated
>
> Can you post it in here, please?
ftp://ftp.ru.openwall.com/pvt/segoon/pub/diff
As you said, it is a basic not tuned config.
> > and a basic .config file is created.
>
> What did you base it on?
>
> I think we should start with OpenVZ's (which is in turn based on RHEL's)
> and tweak from there.
OK.
ftp://ftp.ru.openwall.com/pvt/segoon/pub/dot-config-i686
> > For now it should be 042stab055.16.
>
> Actually, we should go with their testing kernels. By the time we're
> ready to declare any of this stable in Owl, they'll move their testing
> to stable as well (or replace it with an even newer revision, which
> we'll update to). So it'd be 042stab056.11 now.
OK.
1) I've enabled IPv6 for now -- we will enable it anyway and disabling
it would force us to #ifdef many places.
2) Do we need a "/dev/cdrom" patch in init/do_mounts.c? I guess we
should move the decision of real device identification from a raw device
path to a label or smth.
3) We had no USB support in 2.6.18. I guess we need it now.
4) I'd vote for compiling wireless drivers as modules.
Thanks,
--
Vasily
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.
