Upgrading mlDonkey module

[chemist]

I'm using the DONKEY module for quite some time now but want to upgrade to the latest mldonkey version.
Since I don't want to be complete dependent on all the great developers here I was wondering if it is possible and how much trouble it would give to update mldonkey myself.

Some info:
- I know enough about linux to install and configure basic stuff
- I have the DONKEY module installed and running
- I have found the howto for installing the debian chroot / bootstrap

My questions:
Is it just a matter of installing the debian chroot, download the ARM package of mldonkey, configure some things and go or will there be problems to expect ?
Can I just install the new kernel on the same place as the old one (so overwrite it) or should I use another location and delete the old mldonkey afterwards ?
What will happen with my current downloads; will they be migrated or should I start them again (no problem, but nice to know on the beforehand).

[chemist]

I found a simpler (and more elegant) solution.

First I downloaded the precompiled mldonkey for ARM on mldonkey.sourceforge.net/forums/viewforum.php?f=16

Then I disabled the Donkey module on the N2100. I copied the new mlnet to the NAS, chmod 755 it and restarted the donkey module via the web interface.

It looks like it is working OK for now. I will do some more tests and if it stays stable I will see if I can create a new version of the Donkey module.

[chemist]

ok, I got an installing module (took some time due to the ./ thing which I overlooked), but I still have a problem. After installing, the scripts to enable/disable the module don't have the proper rights so I cannot enable/disable the module from the webpage.

I will look into it tonight and see if I can find out where it goes wrong ...

If anyone has an idea why this happens please let me know !!

[chemist]

I got the new module running and tested it briefly.

The module is based on a precompiled OLDABI ARM version of mldonkey 2.9.6.

There appears to be a minor bug in this version: max_BT_uploaders cannot be changed to a value higher than 3 ...
The developers already know this however and everything else in it appears to be working normally.

In case anyone wants it to play around with drop me a message.