SliTaz SliTaz Forum

You are not logged in.

#1 2014-01-18 08:40:36

mzs_47
Member
Registered: 2014-01-01
Posts: 5

Slitaz Torrents?

Hi, I want to download Slitaz packages disc, which is around 3GB in size.

http://www.slitaz.org/en/get/

But the problem is, my network is very slow(256 Kbits/s = 32 KBytes/s), and I will need torrents to download.

This presents some advantages,

I can pause and resume whenever I want. Not download the whole disc in one go.

If there is a power cut(which happens here frequently), I can still resume the download.

Download is verified, so user can be assured that the image is good.

However supporting torrents might be  a problem if you are indeed generating that image everyday. Which I presume is not everyday.

I use torrents to download Debian package DVDs and latest version of Libreoffice. It is really a boon for people having slow links or unreliable connection. And helps you to save bandwidth.

So is it feasible to officially support torrents?

Thanks!

Offline

#2 2014-01-18 14:08:01

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: Slitaz Torrents?

It's a possibility. Setting up a Transmission web client isn't too hard and this is one of the few legitimate (and legal) uses for torrents.

Offline

#3 2014-01-18 22:16:54

holkfoor
Member
Registered: 2013-03-09
Posts: 41

Re: Slitaz Torrents?

You can use the Xterm with Wget.

Example: [c]wget -c http://your-link...[/c]

(*) If you lose power, use the same command for the same file. Wget checks and continues the download.

(*) You can also stop the download (Ctrl+c) at any time and continue later (wget -c).

Offline

#4 2014-01-19 04:23:49

mzs_47
Member
Registered: 2014-01-01
Posts: 5

Re: Slitaz Torrents?

@T_za, will be great if Slitaz can support this. Many users will be happy to show support by seeding smile

@holkfoor, thanks! I will try this out.

Regards.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]