Re: [2.0] Plans for next beta version (1.9.18/1.9.19)

"Gilles Espinasse" <[email protected]>
Newsgroups gmane.comp.security.ipcop.devel
Message-ID <110f01cbc444$87c92e00$f9b5a8c0@pii350>
----- Original Message ----- 
From: "Olaf Westrik" <weizen_42-Yz37vSk3/[email protected]>
To: <[email protected]>
Sent: Friday, February 04, 2011 8:51 AM
Subject: Re: [IPCop-devel] [2.0] Plans for next beta version (1.9.18/1.9.19)


>
> ... some time has past ...
>
>
> Anyways, many things have happened (not all related to IPCop though ;-))
> recently.
>
>
> I have listed:
>   - update util-linux to 2.19 as soon as it becomes available
>   - update dnsmasq to 2.56
>   - Achim is working on some basics for email reporting
>   - Marco is working on proxy etc. That'll probably take more time, so
> not relevant for next release.
>
>
> I am currently uncertain about Perl. There have been several changes in
> the 5.12 branch that need a closer look. At first look 5.10 appears
> unmainted, so we would probably need to consider changing to 5.12
>
>
> Olaf
>
Concerning perl, a 5.10.2 may happen. But no news in january.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2010-12/msg00600.html

We may still follow ubuntu-10.04 perl-5.10.1 package or RH6
http://packages.ubuntu.com/maverick/perl

I agree we could consider perl-5.12. This is not so deep in my todo list.

I would hope soon to:
- conclude my env build cleanup this week-end,
- fix floppy build
* vmlinuz compiled with -fno-stack-protector in CFLAGS produce random
characters on screen when initramfs start and hang
* vmlinuz compile without STACKPROTECTOR set in config work. But that fail
to insmod modules compiled with STACKPROTECTOR
* so the simple solution is revert using standard vmlinuz and remove again
cd support from floppy

- try to fix gcc for other arch since it is hardened.
I need to check what debian patch match the patches we include.

Gilles


------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.