I will host the ISO and other if I can get it to work or try too. Transmission is part of Porteus so lets use it.Let's start from the beginning, how do I create a new .torrent file:
1. Choose the tool I'll be using: transmission-create (a console tool);
2. See what options do I have:
3. Create the .torrent:Code: Select all
$ transmission-create -h Usage: transmission-create [options] <file|directory> Options: -h --help Display this help page and exit -p --private Allow this torrent to only be used with the specified tracker(s) -o --outfile <file> Save the generated .torrent to this filename -c --comment <comment> Add a comment -t --tracker <url> Add a tracker's announce URL -V --version Show version number and exit
4. Check the result:Code: Select all
$ transmission-create --private --comment "Just an example" --tracker "udp://tracker.openbittorrent.com:80/" --outfile example.torrent Something.mp4 Creating torrent "example.torrent" ........................................................... done!
In point 3, the file name could have been given using the full path, say /external/videos/documentaries/Something.mp4; that path is not recorded in the .torrent, just the file name. Same goes if the contents is a directory, the full path is not recorded, just the directory. When you use the .torrent file the file/directory name becomes relative, you'll see how below.Code: Select all
$ transmission-show example.torrent Name: Something.mp4 File: example.torrent GENERAL Name: Something.mp4 Hash: 70390... Created by: Transmission/2.33 (12565) Created on: Wed Aug 10 12:01:20 2011 Comment: Just an example Piece Count: 1099 Piece Size: 1.00 MiB Total Size: 1.07 GiB Privacy: Private torrent TRACKERS Tier #1 udp://tracker.openbittorrent.com:80/ FILES Something.mp4 (1.07 GiB)
The tracker I used works w/o having to register the torrent with them, the original .torrent file can be used with no other steps involved (you still have to make that .torrent file or the equivalent magnet link available to your peers so they can download).
Then I upload the .torrent file to my server, say (continuing to use terminal tools):
The server will look at its "download" directory, as in:Code: Select all
$ transmission-remote --add example.torrent
If it finds the contents, then verifies that it is the same file (the .torrent file contains 'checksums' for every piece), and starts seeding. If it doesn't find it, then tries to download unless I also specified to start paused (--start-paused).Code: Select all
$ transmission-remote hpmediavault -n user:password -si VERSION Daemon version: 2.33 (12565) RPC version: 13 RPC minimum version: 1 CONFIG Configuration directory: /opt/var/transmission/config Download directory: /opt/var/transmission/downloads <-------------- Download directory free space: 496.3 GiB Listenport: 2310 Portforwarding enabled: No uTP enabled: Yes Distributed hash table enabled: Yes Local peer discovery enabled: No Peer exchange allowed: No Encryption: preferred Maximum memory cache size: 12.00 MiB LIMITS Peer limit: 600 Default seed ratio limit: 1.50 Upload speed limit: 195 KiB/s (Enabled limit: 195 KiB/s; Disabled turtle limit: 100 KiB/s) Download speed limit: Unlimited (Disabled limit: 1.00 MiB/s; Disabled turtle limit: 1.00 MiB/s) MISC Autostart added torrents: Yes Delete automatically added torrents: Yes
Now if I wanted to use a different location on the server instead of its default download directory:
The sample.torrent file is the same;
The location can be changed when I load the .torrent:
Or it can be changed "after the fact". Transmission-remote has parameter --move, Transmission-Qt has "Set location...", and so forth.Code: Select all
$ transmission-remote --download-dir /usbdrive/seeds/documentaries --add example.torrent
.