Re: Progress on 2.1

Hi Gilles!

> I slowed probably the process a lot with my suggestion to use the 3.4 kernel. I haven't found time to progress faster.
> Any issue compiling external driver for 3.4 should be fixed now as sangoma released wanpipe-7.0.x
> The big jump in the release number from 3.5.28 mean nothing for the code, only a sync with the windows driver version number.
> I haven't yet compiled that crap code.
> 
> I am compiling those days ipcop with kernel 3.4.37 and I have seen 3.4.38 should arrive soon.
> 
> I haven't had the time to test the install a lot with 3.4 and tune the kernel config.

May you can commit the kernel 3.4 upgrade stuff you already have and others can
test+modify it?!

IIRC I read somewhere kernel 3.0 should be EOL oct 2013. So we really should
upgrade to 3.4 for 2.1.x.


> Probably we should update perl to debian wheezy (5.14.2.20..) or in a bit more than one year, our old perl will not be maintained anymore.

I'm currently upgrading Perl to Debian Wheezy (5.14.2-x). I have tweaked
lfs/perl like described in LFS 7.1 and both toolchain and base are compiling
fine. The Perl rootfile is already changed but needs some testing if something
is missing.
Too the old Perl 5.10.1 is 'rm -f ...' in update-2.1.0-setup (needs testing).
The update-rootfiles probably needs some more (new) Perl files, have to check
this. Only want to have the regular Perl rootfile working before working on the
update rootfile.

Is there anything else I have to tweak/look into?

best regards,
Achim

PS:
Want to push 2.1.1 forward...

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may