jdong
January 11th, 2007, 11:08 PM
For those who don't know, KTorrent is light(ish)weight, feature-rich BitTorrent client written with KDE libraries (but it runs fine in GNOME, much lighter than Azureus to say the least!)
2.1RC1 represents a major upgrade to the 2.0.3 series. It now is one of the only Linux clients that supports (in parentheses are other clients that support the functionality mentioned under Linux):
* Mainline DHT with full support for creating and using decentralized torrents (uTorrent+WINE and BitTorrent Mainline have full support, Deluge and rtorrent can use decentralized torrents but not properly create them. Azureus uses an incompatible DHT implementation)
* uTorrent Peer Exchange for acquisition of more peers when trackers aren't available or are peers are dispersed amongst several trackers (uTorrent+WINE is the only other client to support this, Deluge will at 0.6-ish. Azureus will support this standard in the future too, but currently uses its own incompatible PEX)
* Reasonable RAM usage, 30MB RSS or less when downloading 2 DVD Linux ISO's (uTorrent+WINE [somewhat disputed because WINE library occupation cannot be measured without kernel memory profiling patchsets], rTorrent, Deluge)
* LAN peer finder for locating and prioritizing peers on the LAN (Azureus)
* Web interface and console interface for remote control (Azureus)
I'd like to introduce KTorrent 2.1 as soon as it releases (in about two weeks) in the dapper-backports and edgy-backports repositories, but I want to make sure that it's reasonably stable before doing so.
In all my testing, 2.1RC1 has been very stable with no bugs I've noticed, and few bugs reported.
Dapper and Edgy debs are available at http://ktorrent.org/index.php?page=downloads , if you have/use prevu, these debs can also be built from Feisty sources as a "backport".
If you are more bleeding edge, you can find SVN snapshot debs at http://ktorrent.org/forum/viewtopic.php?t=1031
Thanks in advance for all your help!
2.1RC1 represents a major upgrade to the 2.0.3 series. It now is one of the only Linux clients that supports (in parentheses are other clients that support the functionality mentioned under Linux):
* Mainline DHT with full support for creating and using decentralized torrents (uTorrent+WINE and BitTorrent Mainline have full support, Deluge and rtorrent can use decentralized torrents but not properly create them. Azureus uses an incompatible DHT implementation)
* uTorrent Peer Exchange for acquisition of more peers when trackers aren't available or are peers are dispersed amongst several trackers (uTorrent+WINE is the only other client to support this, Deluge will at 0.6-ish. Azureus will support this standard in the future too, but currently uses its own incompatible PEX)
* Reasonable RAM usage, 30MB RSS or less when downloading 2 DVD Linux ISO's (uTorrent+WINE [somewhat disputed because WINE library occupation cannot be measured without kernel memory profiling patchsets], rTorrent, Deluge)
* LAN peer finder for locating and prioritizing peers on the LAN (Azureus)
* Web interface and console interface for remote control (Azureus)
I'd like to introduce KTorrent 2.1 as soon as it releases (in about two weeks) in the dapper-backports and edgy-backports repositories, but I want to make sure that it's reasonably stable before doing so.
In all my testing, 2.1RC1 has been very stable with no bugs I've noticed, and few bugs reported.
Dapper and Edgy debs are available at http://ktorrent.org/index.php?page=downloads , if you have/use prevu, these debs can also be built from Feisty sources as a "backport".
If you are more bleeding edge, you can find SVN snapshot debs at http://ktorrent.org/forum/viewtopic.php?t=1031
Thanks in advance for all your help!