Transmission BT
The following tutorial will guide you step-by-step through the process of setting-up Transmission BT on FFP-0.5 running on NSA310 (apparently there is a problem with uClibc in FFP-0.7/oarm).
This tutorial is by Linux Rookie and is meant for Rookies.
STEP 1 - Prepare
If you already have FFP v0.5 up and running proceed to STEP 2, otherwise you’ll need to (re)create your FFP stick:
1.1 Download the zipfile from here and extract all files onto your USB drive (you will need to delete 2nd partition if you’re recreating your stick).
1.2 Before you put your stick into NAS and start standard procedure of setting-up FFP, edit after_booting.sh file on your USB device: find the line with FFPVERSION=auto and change it to FFPVERSION=0.5
Important: Make sure you use an editor that supports Linux line breaks (for Windows users I recommend PsPad).
1.3 Plug USB device into your NSA, reboot and setup the FFP.
STEP 2 – Download and install
(main thread and latest packages for Transmission on FFP here)
2.1 Download following packages:
- curl-7.18.1.tgz
- Transmission 2.50 (ffp-0.5)
To download, run following commands in Terminal:
Code:
wget
http://kylek.is-a-geek.org:31337/files/ ... 7.18.1.tgz
wget
http://kylek.is-a-geek.org:31337/files/ ... 2.50-1.tgz
2.2 Installation
Code:
funpkg -i curl-7.18.1.tgz
funpkg -i Transmission-2.50-1.tgz
STEP 3 – Configuration
(this is not a standard configuration – it just suits me best – you can adjust it to your needs)
3.1 Create three new directories for: downloads, transmission config files and incomplete downloads
Code:
mkdir /mnt/HD_a2/downloads
mkdir /mnt/HD_a2/admin/transmission
mkdir /mnt/HD_a2/admin/transmission/incomplete
3.2 Change the owner of newly created directories
Code:
chown -R nobody:501 /mnt/HD_a2/downloads
chown -R nobody:501 /mnt/HD_a2/admin/transmission
chown -R nobody:501 /mnt/HD_a2/admin/transmission/incomplete
3.3 Run Transmission for the first time
Code:
transmission-daemon -g /mnt/HD_a2/admin/transmission
* -g parameter sets the config-dir (where the Transmission should look for configuration files)
3.4 Stop transmission-daemon
Code:
/ffp/start/transmission.sh stop
STEP 4 – Edit settings.json file
4.1 [optional] You might need to change the ownership of settings.json file to allow editing
Code:
cd /mnt/HD_a2/admin/transmission
chmod 777 settings.json
4.2 Edit settings.json file
- Go to transmission folder in you admin share and open settings.json file in a proper editor (like PsPad for Windows)
- Edit (at least) following lines, so they look like this:
Code:
"download-dir": "/mnt/HD_a2/downloads",
---
"incomplete-dir": "/mnt/HD_a2/admin/transmission/incomplete",
"incomplete-dir-enabled": true,
---
"rpc-whitelist-enabled": false,
---
"umask": 0,
* rpc-whitelist-enabled: set to false gives access to Transmission to all IPs (machines), that’s why it's important to set the password for transmission.
** umask set to 0 grants full access to downloaded files to the world (so you can edit, move and delete downloaded files).
STEP 5 – Start and use transmission
5.1 [Important] In order to start transmission you must always include -g parameter and point it to the config directory of your choice (like when you ran it for the first time). If you don’t do this, Transmission will create a new config file in a different (default) directory and your settings won’t be valid.
To start Transmission:
Code:
transmission-daemon -g /mnt/HD_a2/admin/transmission
5.2 Run Transmission Web interface
http://[your-nas-ip]:9091
>> Other Transmission controls:
Code:
/ffp/start/transmission.sh stop # stop transmission
killall transmission-daemon # kill all transmission processes
/ffp/start/transmission.sh status # status of transmission
------------------------------
Daca deschideti http://[your-nas-ip]:9091 ar trebui sa apara ceva de genul acesta :
