DSM-G600, DNS-3xx and NSA-220 Hack Forum

p.r. · 2008-05-28 16:41:45

What torrent client should I choose for DSM-600(ppc)?
It must work quick, support traffic encryption and it must be allowed (recommended) client at many trackers.

I have some small experience with rtorrent/libtorrent, but at x86-platform (linux slackware).
I'd like to continue to use it (rtorrent/libtorrent) if it's possible to compile it for DSM-600(ppc).

In "How to fun_plug" and "Telnet login" sections everything is simple for me, but where to start in compiling torrent client is not yet clear.

Could you advise me, what torrent client to choose for D-Link DSM-600(ppc), and where to start?

sala · 2008-06-12 00:04:19

transmission is good pick
Download section has some old versions but I recommend to compile newer version (1.06 or newer).

Many users use mldonkey but I have'nt tryed it. Also I am not sure how private trackers like it.

p.r. · 2008-06-14 15:17:06

I decided not to abandon the original idea of cross-compiling rtorrent_0.7.9/libtorrent_0.11.9.
But now it seems to me I hit the trap because of a badly outdated firmware or maybe of source code from D-Link (?).

I managed successfully cross-compile dtach 0.8, zlib 1.2.3, libsigc++ 2.0.18, ncurses 5.6 20071201, libidn 1.8, openssl 0.9.7m, curl 7.17.1, libtorrent 0.11.9.

But when I tried to cross-compile rtorrent, the following error occurred:
"... libtorrent.so: undefined reference to` mincore '
collect2: ld returned 1 exit status ... "
I used uclibc-toolchain-src-20040609 from D-Link.

On how much I understand, uClibc 0.9.26 library in uclibc-toolchain-src-20040609 has no support for system call mincore().
This system call was implemented for uClibc 0.9.26, but a little later - 2004/12/19 (http://www.by.kernel.org/pub/linux/libs … gelog.full).

???:
How can I know what is revision of uClibc 0.9.26 in firmware?
or
How can I substitute uClibc 0.9.26 to a new revision with mincore() support, but without reflashing firmware?
or
Maybe the problem is something else, rather than the lack of mincore() support in uClibc 0.9.26 (20040609)?

Thank you in advance for any advice or information.

Last edited by p.r. (2008-06-14 15:21:10)

p.r. · 2008-06-15 15:06:51

It seems I've resolved the problem with mincore.

I built again cross-toolchains with more new (about the end of December 2004) than in D-Link source code revision of uClibc:
1. mkdir /uClibc-0.9.26
2. svn co -r 9590 svn://uclibc.org/trunk/uClibc /uClibc-0.9.26
3. tar -cjf /uClibc-0.9.26.tar.bz2 /uClibc-0.9.26
4. cp /uClibc-0.9.26.tar.bz2 /powerpc-uclibc-toolchain/sources/dl
5. cd /powerpc-uclibc-toolchain
6. make

Then, I re-cross-compiled libtorrent, and the problem with mincore during cross-compilation rtorrent disappeared.

And now I have everything nedded to run rtorrent:
libcrypto.so.0.9.7
libcurl.so.4.0.1
libgcc_s.so.1
libidn.so.11.5.37
libncurses.so.5.6
libsigc-2.0.so.0.0.0
libssl.so.0.9.7
libstdc++.so.5.0.5
libtorrent.so.10.0.8
libz.so.1.2.3
and indeed rtorrent itself!

Even more I've managed to run rtorrent!
But so far, it still means nothing.
It needs to be tested in real work.

Last edited by p.r. (2008-06-15 15:09:03)

sala · 2008-06-16 09:00:00

Looks good, but one thing though, you cant use dtach because lack of a unix domain socket support. Although custom firmware will add them, but you must be ready do give up some of the original firmware features like upnp.
Second option you have is to use loader.o to boot up custom kernel with unix domain socket support.

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1 2008-05-28 16:41:45

Torrent client

#2 2008-06-12 00:04:19

Re: Torrent client

#3 2008-06-14 15:17:06

Re: Torrent client

#4 2008-06-15 15:06:51

Re: Torrent client

#5 2008-06-16 09:00:00

Re: Torrent client

Board footer