Chimbo, another question. Besides cpu/memory usage. What is the download speed you achieve with your torrents? I'm still not passing from 30KB/s (maximum!!), with an average of ... 5 or 10KB/s

Thanks, I got it running w/no problems. Now I have to figure out how to get Dropbear to start automatically--that is without my having to fire it up manually every time I reboot the box. What I am, hence, looking for is the Linux equivalent of the Startup folder in Windows. This is, as a matter of fact, a general problem that is in no way specific to Dropbear: how would I be running a program automatically at startup or, even better, as a service (I believe it's daemon in Linux lingo, right?)?

Now, I didn't bother scouring the Linux manuals in search of this info just because it may be that setting this up in an embedded Linux environment like my/our Airlive box may be quite different than setting it up on a normal Linux desktop PC. (If it ain't, I'd appreciate your simply posting a link--no need to start explaining it here from scratch.)

Finally, I don't suppose any of the Linux aficionados reading this forum have given some thought to compiling Deluge for the Airlive device, have they?

better way is download this: http://mgb111.pradnik.net/addons/libs-essential-20080502.tar.bz2

dropbear is a daemon, always.
http://mgb111.pradnik.net/addons/rc-local.example.txt

libz is in flash image. duplicating is not needed.

yes, i compile software in uclibc - native. And everyone may use  basic env "uclibc-basic.tar.bz2" (unarchived on other linux, and chrooted) to compile software, and libraries if neeeded (not firmware). Or may build bootable linux with this.

Ok! Just a word to explain: I tried this with my mbg100, which has no libz in /lib
chimbo

Hi,
I can confirm that with the uclibc-basic.tar.bz2 environment the native build is relatively easy (even for me with limited linux knowledge). Prior that I tried to build the uclibc environment on my own (with JoKeR's buildsystem config file), but now - with all these pre-built essential libs it is much simpler, co thanx for the bonus JoKeR ;-)

I have just almost-succesfully compiled the subversion 1.4.6 (along with swig-1.3.27 for svn python bindings) and mod_python 3.3.1 for Apache. Almost succesfully means that although the svnserve is up and running, the svn client builds ok, but has some problem with locales, loader writes "svn: can't resolve symbol '__ctype_tolower'" during the launch. Disabling the locales support in svn (--disable-nls) did not solve the problem. I have found some workarounds on web (based on renaming the __ctype_* symbols family to __ctype_*_loc) though was not successful at that. I do not actually need the svn client on the box but am still wondering what I am doing wrong.

For the deployment of built binaries, I currently parametrize the configure script with --prefix pointing to /mnt/C/sys and then gzipping all the files based on its date/time, but it seems to me little bit error prone (for example in case the make install made some changes outside the sys directory).

So I'd like to ask:
1) Did anybody (namely JoKeR) encounter such problem with symbols and if so, do you know a solution?
2) How do you automate the deployment? Is there a more elegant way to do that? (possibly directly from the configure/make)

Thanks in advance.