Setting up Java 8 on Ubuntu

After spending a few days searching the web for a way to install the latest Oracle version of the Java Developers Kit I was relieved to find a team of people that produce an easy to install package for Oracle’s Java.

To begin we are going to add the PPA to our machine and then install the main installer. To do so run the following command:

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer

During the last command a screen will appear, this will ask you if you agree to the Oracle Binary License. You will need to agree to this to continue. When finnished you have installed Java and can check by running the following command:

java -version

If this return something like below then Java has been installed correctly:

java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)

Finally, to set up the JAVA Enviroment you can use another package by the same team. To do so run the following command:

sudo apt-get install oracle-java8-set-default

That’s all there is to it and you have now set up Oracles Official JDK on Ubuntu. The team behind this are absolutely amazing for doing this. It makes the whole process so much easier to install than when I was looking at the way to this manually.

Installing Sick Beard on the Raspberry Pi

In this tutorial I will detail how to install Sick Beard on the Raspberry Pi, specifically, on Raspbmc. It is really easy to install Sick Beard but you will need to install git to get Sick Beard.

To install Git run the following command:

sudo apt-get install git-core

When this is finished you will have git installed. This is a version management system that allows easy code development. Now we are going to download the latest copy of Sick Beard using git. The following command will download Sick Beard in the current directory:

git clone git://github.com/midgetspy/Sick-Beard.git my-sickbeard-install

You now have a copy of Sick Beard, you can either start it or move it to another directory. To start SickBeard run the following command:

python my-sickbeard-install/Sick-Beard.py

If you want to move the Sick Beard installation then running the following commands will move SickBeard to ‘/sickbeard’

sudo mv my-sickbeard-install/* /sickbeard/
$  sudo chmod 777 /sickbeard

There we go, that’s all there is to it. You can now start using SickBeard through the web browser at the web address:

 http://IPADDRESS:8081

 

Installing Handbrake to RIP DVD’s

Should you want to backup a DVD, this tutorial will detail how to install and set up Handbrake to do so.

The first thing that you need to do is install Handbrake with the following command:

sudo apt-get install handbrake

Now we need to install a package called Libdvdcss so that we can access encrypted DVD’s so run the following command to install the main package:

sudo apt-get install libdvdread4

If you have installed the Ubuntu Restricted Extras package from the Software Centre this has already been installed.

Finally to install the Libdvdcss package run:

sudo /usr/share/doc/libdvdread4/install-css.sh

That’s all there is to it! You can now backup your DVD’s with Handbrake!

Installing Transmission onto your GoFlex Home

Transmission is a great option when it comes to Torrent software, when paired with the GoFlex Home (A NAS that comes in 1TB, 2TB or 3TB variations), it can become an invaluable tool to have as the NAS is likely to be running most of the time. After searching around the web for a bit I found a way to install transmission by simply copying a few file around the place.

The first thing you need to do is download the package from the OpenStora Site (I highly recommend this site if you have any device powered b the Hipserv operating system, this tutorial is a detailed version of there instructions). You will need to register to download the file. When you have downloaded the file from OpenStora, you will need to move onto the NAS. In this example, I moved it to the Public share on my user ‘server’.

Now you can extract the files and get ready to move them around. To extract them run the following command:

tar xvfz transmission-1_92_ARM_Stora_tar.gz
cd transmission

Now we have all of the files ready however, before we do that, we should edit them before moving them. There is only one file that we need to edit right now. So open the file in the vi editor with the command below:

vi init.d/transmission-daemon

There are two settings in this file that we need to edit. We need to set the config path and the username. For this example, I am going to user the user server and put the files in the users home. This is what I changed it to:

TRANSMISSION_HOME=/home/server/config/transmission-daemon
DAEMON_USER="server"
Before you can edit a file in vi you need to press the ‘i’ key to enable editing.

This means that the user server should be able to edit all of the configuration files as it is in the user home directory, but to be sure and create the directory run the following commands:

sudo mkdir -p /home/server/config/transmission-daemon
sudo chown server:server /home/server/config/transmission-daemon
Remember to replace the details in the command with the details for your user and path if you are not using the same as I have

Now you can exit the file and begin moving them around. The following commands will move all of the file to the correct location:

sudo mv transmission-daemon /usr/local/bin/
sudo mv init.d/transmission-daemon /etc/init.d/
sudo mv web/index.html /usr/share/transmission/web/
sudo mv web/images /usr/share/transmission/web/
sudo mv web/javascript /usr/share/transmission/web/
sudo mv web/stylesheets /usr/share/transmission/web/

Now that all of the file have been moved, we can start and stop the transmission-daemon so that it generates the configuration file. To do so run the following commands:

/etc/init.d/transmission-daemon start
/etc/init.d/transmission-daemon stop

Finally, we can change the settings in the file that was just generated. To do so open the ‘settings.json’ file located in the TRANSMISSION_HOME directory. The following command works for the example used in this tutorial:

vi /home/server/config/transmission-daemon/settings.json

There are a few options in here that should or could be edited. The information below details all of this with the settings that I used for this tutorial.

File Locations

Setting Information Example
download-dir Where finished downloads are stored \/home\/server\/GoFlex Home Public\/Downloads\/Finished
incomplete-dir Where downloads are stored before they are finished, ie where they are stored whilst they are still being downloaded. \/home\/server\/GoFlex Home Public\/Downloads\/Incomplete
incomplete-dir-enabled Allows you to enable the incomplete directory true
watch-dir The directory Transmission should watch for torrent file to automatically add and download \/home\/server\/GoFlex Home Public\/Downloads\/Add
watch-dir-enabled Allows you to enable the watch directory true

Security

Setting Information Example
rpc-authentication-required Requires password to access the Web GUI, set to false to disable true
rpc-username The username to access the Web GUI when the Authentication is enabled MyUser
rpc-password The password to access the Web GUI when the Authentication is enabled This is a password!
rpc-whitelist-enabled This allows you to enable an IP address white list to only allow specific IP address to access the Web GUI false

When you have finished editing the file you can save it and start the daemon again with the command:

/etc/init.d/transmission-daemon start

You should now be able to access the Transmission Web interface at:

http://goflexip:9091

Start on boot

The final option is to set up Transmission to start when the computer boots. To do so run the following commands:

sudo /sbin/chkconfig –add transmission-daemon
sudo /sbin/chkconfig –levels 2345 transmission-daemon on

That’s all there is to it, you are now running Transmission on the embedded device in you GoFlex NAS. Unfortunately, you can not access the daemon with the remote program as the Transmission version is 1.9.8, which isn’t supported.

SSH Access to the Seagate GoFlex Home

The Seagate GoFlex Home is the NAS that I currently use, with a 2TB drive it is a perfectly capable drive for basic needs. It also allows you to SSH into the device its self. To do so you will need to the run the following command:

ssh USERNAME_hipserv2_seagateplug_XXXX-XXXX-XXXX-XXXX@IPADDRESS

Simple replace ‘USERNAME’ at the start with your username for the device and ‘XXXX-XXXX-XXXX-XXXX’ with the Serial Key from the base of the device. The code is usually the largest, at the bottom and starts with a code like ‘PK:’. Don’t forget to add the IP address where it says ‘IPADDRESS’.

The ‘PK:’ at the start isn’t part of the key, you do not use this in the ssh command.

That’s all there is to it. You can now SSH into your device to run any commands that you want.

How to update the Raspberry Pi Firmware

So whilst I was looking to install XBMC on my Pi, I found an easy way to update the firmware with only a few commands. This is basically a cut down version of the official instructions by Hexxeh.

To begin, SSH or log into your Pi, when you have connected run the following commands:

sudo apt-get install rpi-update
sudo rpi-update

That’s all there is to it, you can now make any changes that you need to (such as Memory splits) and finally, reboot the machine to start using the new firmware with the following command:

sudo reboot

For the full instructions on how to update and modify the Pi’s firmware visit the official GitHub page.

Deluge on Pi

Deluge is a brilliant bit of software to download torrents. What’s even better is the fact that you can run Deluge on a Raspberry Pi, allowing you to easily create an always on torrent box. In this tutorial I will cover how to install the packages and set them up so that you can run an always on torrent box with a Raspberry Pi. It will also allow you to connect via the ThinClient system from another computer or via the web from any device. To begin you will need to either be at the Raspberry Pi, or connect to it via SSH. When you have connected you may wish to update the computer. To do so run the following commands:

 sudo apt-get update
sudo apt-get upgrade

Now that the Pi is up-to-date, we need to install the two packages that will provide us with all of the functionality that we will need. Choose the command that best suits you need (With or without the web interface):


Deluge with Web Interface

sudo apt-get install deluged deluge-web

Deluge without Web Interface

sudo apt-get install deluged deluge-console

When the packages have finished installing, we need to start the Deluge Daemon so that it creates all of the configuration files that we need. To do so run the following commands:

 deluged
pkill deluged

We can now add a user to the configuration. This isn’t the user for the Pi but the user name and password that you will use when you log through the ThinClient. There are four levels that the user can have, these will change what kind of access that use has to the Deluge system.

Number Level
0 No Access
1 Read Only
5 Normal
10 Administrator
Before you add the user to the configuration, you should know that the password will be stored in plain text. Therefore, you should think about what password you are using carefully.

To add a user to the configuration, you will need to run the following command replacing the information with the information for your user.

echo “username:password:levelnumber” >> ~/.config/deluge/auth

Now, we need a way to easily start and stop Deluge. To achieve this we are going to download a script written by QuidsUp. Choose the command that best suits your needs:


Deluge with Web Interface

wget http://dl.izzard.me/RPi/deluge/full
mv full deluge
nano deluge

Deluge without Web Interface

wget http://dl.izzard.me/RPi/deluge/core-only
mv core-only deluge
nano deluge

In the file you need to look for two lines like below:

#Required -- To be changed!
USER=username        #Set Username here.
PORT=8112            #Set port number for web interface (default 8112)
The line with the PORT=8112 will not be present in the version without the Web Interface

You should fill in your details replacing ‘username’ with your Linux username, not the username that we entered into the file earlier. The Port can be left as is and should only be changed if you need to change what port the web interface runs on. Once saved, we can move the file into the correct directory to run. To do so run the following commands:

 sudo mv deluge /etc/init.d cd /etc/init.d
sudo chmod 755 deluge
update-rc.d deluge defaults

Deluge is now set up and you can start it with the command below:

service deluge start

Deluge with Web Interface

Now that Deluge is fully running we can connect to the computer via the web using the site:


http://computerip:8112

When the interface loads you will be prompted for a password, by default this is ‘deluge’. After you have changed the password click Daemon in the menu at the side and check ‘Allow Remote Connections’ as shown in the picture below and click apply. Deluge Daemon

Due to the fact that the WebUI will only be connecting to a single Daemon, we can set the default daemon in the configuration so that it doesn’t ask us what to connect to each time. To do this run the following commands:

sudo service deluge stop
cd ~/.config/deluge
nano web.conf

Move through this file until you find the section:

"default_daemon": ""

Change the line so that it reads like so:

"default_daemon": "127.0.0.1:55846"

The WebUI shouldn’t ask for the connection when you connect now which removes a step. This isn’t necessary but is a nice feature.


Deluge without Web Interface

Now that Deluge is running we need to enable the setting to allow remote connections. With out this you will not be able to connect to the Daemon. To enable remote connections we are going to use deluge-console, to start the console and change the setting run the following command:

deluge-console
config -s allow_remote True
config allow_remote

If the console returns True, the change was successful and you can exit the console with the following command:

exit

That’s all there is to it, you can now use your Raspberry Pi as an always on Torrent Box for all your downloading needs.

Connecting Raspberry Pi to Seagate GoFlex Home NAS

The Raspberry Pi is great, other than the storage in the device is quite small for a computer. As such it is often desirable for quite a few Raspberry Pi projects to connect it to some form of external storage. In this tutorial I will show you how to connect the Raspberry Pi (And possible other Linux based computers) to a Seagate GoFlex Home.

To start you need to log into the Raspberry Pi via SSH (Or be at the computer). For this tutorial, we will be mounting the GoFlex in:

/mnt/goflex/

However, if you read the comments for the script then you will be able to change this to whatever you like. As such we need to create a few directories to ensure that we can mount the NAS. To do so, run the following commands:

sudo mkdir -p /mnt/goflex/public /mnt/goflex/personal /mnt/goflex/backup

Now that we have all of the directories that we need we can download the scripts. To do so we need to move into the directory and download two scripts, use the commands below:

cd /mnt/goflex
sudo wget http://dl.izzard.me/RPi/goflex-mount/.goflex_auth
sudo wget http://dl.izzard.me/RPi/goflex-mount/connect.sh

The two scripts we have just downloaded will allow us to easily connect to the NAS manually if we wish and to also connect at boot. Now we need to edit the first file that will contain our login information. To do so open up the file with the command below:

sudo nano .goflex_auth

The file will contain the code shown below, simply remove the capital letters and insert your details for the GoFlex:

username=USERNAME
password=PASSWORD

Now, there is only one more change that we need to make but this time it’s to the connect script so save and exit nano (CTRL + X) and run the command bellow:

sudo nano connect.sh

In this file you need to find the line that reads like below:

IP=''

Then change it to the IP address of your GoFlex. You can then save and exit nano (CTRL + X).

The IP address should not contain any slashes or other characters. Only use the numbers otherwise the script will not work correctly.

Before we continue to the next step we should test the script to ensure that all the details are correct. To do so run the following commands:

sudo bash connect.sh
cd /mnt/goflex/public
ls

You should now be able to see all of your private files. If you do not or if there is an error then double check all of the information that you have entered.


Connecting at boot

To make the Raspberry Pi connect to the GoFlex automatically at boot up, we need to add a small snippet of code to the file ‘rc.local’. This will then be run at start up and connect us to the GoFlex. To begin open up the file in nano with the command below:

$  sudo nano /etc/rc.local

In this file, scroll down and add the code:

bash /mnt/goflex/connect.sh

ABOVE the line that reads:

exit 0

When done simply save and exit the file (CTRL+X) and your done. Reboot the Pi and you should automatically be connected to the GoFlex.

Thats it for this tutorial but for more information about the scripts used in this tutorial check out the info page.

Setting up a MoonQuest Server

To the Moon! That’s where every Minecraft player should go. The Yogscast have been releasing a series of videos where Simon, Lewis and Duncan try to fly to the Moon and to Mars (Watch it HerePlease note that I am not involved with the Yogscast, I am simply writing a tutorial about settings up a Minecraft Server so that you can play the same game). So with the Unofficial release of a Mod Pack that allows users to fly around the solar system in their own space craft, you may just want to put it on a standalone server.

For this tutorial, we will assume that you have a server that you know is capable of running a Minecraft environment. If you haven’t then you have to options, re-purpose and old/set up a computer to work as the server or rent a dedicated server from a Game server provider such as Host Horde (Who we use for this tutorial). Now lets set up a server:

  1. The first thing that you need to do is download the Launcher and mod pack. For this we will use the ATL Launcher as it has built in support for the mod pack.
    1. Go to the ATL Launcher websites Download Page
    2. Download the correct version of the launcher (ie, Windows, Mac or Linux)
    3. If the File is in your downloads folder, move it into it’s own empty folder
    4. Run the file to install the ATL Launcher
  2. Set up the ATL Launcher to work with MoonQuest
    1. Go to the Account Tab and Login with your Minecraft/Mojang account
    2. Go to the Packs Tab and scroll down until you find MoonQuest
    3. Click ‘New Instance’ and follow to on-screen instruction, for our Installation we did not enable any extra Mods however it is possible to enable some and it not cause any problems
    4. Follow the Instructions to set up the Instance, you may have to download some mods from the Internet (ATL will open the download page automatically). Just save them in one of the locations listed and you will be ok.
  3. Go back to the Packs Tab and click ‘Create Server’ under the MoonQuest Pack Info, use the recommended install.

Now you have the files you need to run MoonQuest and the files that you need to run the server. We now need to edit the server files so that they will work correctly.

  1. Go to the server files
  2. Run the appropriate start script (Bat file for windows, sh file for others)
  3. Wait for the server to finish creating files and then stop the server (Close the terminal)
  4. Now you can delete the Following Files
    • LaunchServer.bat (Do not delete if running on your own computer without a Control Interface)
    • LaunchServer.sh (Do not delete if running on your own computer without a Control Interface)
    • forge-1.6.4-9.11.1.953.jar
    • server.log
    • server.log.lck
    • CustomRecipes.log
    • ForgeModLoader-server-0.log
    • ForgeModLoader-server-0.log.lck
    • NBTEdit.log
    • NBTEdit.log.lck
  5. Now we need to replace one of the files that we just deleted, if you don’t you will run into a problem with some of the Games ID’s when connecting to the server.
    1. Go to the Forge Download Page
    2. Download the latest universal version of Forge for Minecraft 1.6.4 (We are using version 9.11.1.965)
    3. Place the newly downloaded file into the root of the server files
  6. Now you need to prepare the files to be transfered to the server. Some hosts require that the files be in a certain location, so now is the time to make these changes.
    • If you are using Host Horde, move the following files to a new folder called jar
      • minecraft_server.1.6.4.jar
      • The forge Universal that you have downloaded
      • The folder called libraries
  7. Now you can connect to your server via FTP and upload all of the files as they are to the server
  8. Finally, change the jar name in your server’s control panel to match the Forge Universal (If you are using your own computer without an interface then use the LaunchServer File) and click Start
  9. Now you can connect to the server as you would any other server

That’s all there is to it. You can now connect to the server as you would any other server and play with others.

How to make the Eclipse IDE portable (Installing Java)

The Eclipse IDE is a great tool for development. It will also work from a USB stick, as long as you have Java, however, some computers may not or may be set up wrong (For example, no PATH Variable). Therefore, it can be useful to install Java directly onto the memory stick so that you can take it with you. Before starting this tutorial, you will need to have already installed Java on a computer, if you haven’t you will need access to a computer with Java installed on it. You should also be aware that it may be breaking IT Policy for some organisations to use portable software.

To begin, ensure that you have installed Java on your home computer (You should have installed the Java Development Kit on your computer to use Eclipse fully).. Now you can follow the steps below :

  1. Download a copy of the Eclipse IDE if you haven’t done so yet, and unzip the files to location of your choosing, it should however be on a removable device (Such as a USB Device).
  2. Now we can install Java onto the USB Drive, to beign, find where Java is installed on your computer. This is usually something like “C:\Program Files\Java\jdk1.7.0_51″ however, the final folder “jdk1.7.0_51″ will change with time as this is the version number. In this folder is the files for Java Development and the Runtime Environment. Select all of the files and copy them.
  3. Go to the USB drive and folder where you have installed Eclipse, noe create the folder “jre” and paste all of the files and folders from the Computers Java install into here.

That’s all there is to it! Your Eclipse should now open and allow you to run it from any computer.