Amahi Wiki - User contributions [en]

Installing HDA on HP Mediasmart Server

2012-10-29T14:31:47Z

Sc4s2cg: /* Modifying Ubuntu for Amahi */

Installing your HDA on an old [http://en.wikipedia.org/wiki/HP_MediaSmart_Server HP MediaSmart server], previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* [http://www.ubuntu.com/download/server Ubuntu Server 12.04 LTS], not the desktop version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.

2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.

3. Do NOT install Amahi yet.

4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [[Key-based SSH Logins With Putty|Putty]]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [[Install VNC server on Ubuntu Server 12.04|install a VNC server]] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-29T14:31:00Z

Sc4s2cg:

Installing your HDA on an old [http://en.wikipedia.org/wiki/HP_MediaSmart_Server HP MediaSmart server], previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* [http://www.ubuntu.com/download/server Ubuntu Server 12.04 LTS], not the desktop version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.

2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.

3. Do NOT install Amahi yet.

4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [[Key-based SSH Logins With Putty|Putty]]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-25T14:36:31Z

Sc4s2cg: /* Installing Ubuntu */

Installing your HDA on an old [http://en.wikipedia.org/wiki/HP_MediaSmart_Server HP MediaSmart server], previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* [http://www.ubuntu.com/download/server Ubuntu Server 12.04 LTS], not the desktop version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.

2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.

3. Do NOT install Amahi yet.

4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

McMyAdmin

2012-10-25T14:33:34Z

Sc4s2cg: /* Installing the Tekkit Server */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code|wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin/minecraft}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

===Creating a Tekkit Script===
This is only required if you are striving to have a Vanilla and Tekkit server running side by side.

Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|nohup ./start.sh}}

=Tekkit with McMyAdmin=
------------------
'''Please note that this section was written before McMyAdmin had an option for Tekkit. To make vanilla and TekkiT Minecraft versions run simultaneously, you should also create the Tekkit script from above.'''
------------------

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:25:28Z

Sc4s2cg: /* Tekkit with McMyAdmin */ Spelling, formatting

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

===Creating a Tekkit Script===
This is only required if you are striving to have a Vanilla and Tekkit server running side by side.

Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|nohup ./start.sh}}

=Tekkit with McMyAdmin=
------------------
'''Please note that this section was written before McMyAdmin had an option for Tekkit. To make vanilla and TekkiT Minecraft versions run simultaneously, you should also create the Tekkit script from above.'''
------------------

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:24:24Z

Sc4s2cg: /* Creating a Tekkit Script */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

===Creating a Tekkit Script===
This is only required if you are striving to have a Vanilla and Tekkit server running side by side.

Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|nohup ./start.sh}}

=Tekkit with McMyAdmin=
------------------
Please note that this section was written before McMyAdmin had an option for Tekkit. To make vanilla and Tekki Minecraft versions run simultaneously, you should also create the Tekkit script from above.
------------------

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:23:08Z

Sc4s2cg: /* Installing the Tekkit Server */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

===Creating a Tekkit Script===
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|nohup ./start.sh}}

=Tekkit with McMyAdmin=
------------------
Please note that this section was written before McMyAdmin had an option for Tekkit. To make vanilla and Tekki Minecraft versions run simultaneously, you should also create the Tekkit script from above.
------------------

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:22:56Z

Sc4s2cg: /* Tekkit with McMyAdmin */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

=Tekkit with McMyAdmin=
------------------
Please note that this section was written before McMyAdmin had an option for Tekkit. To make vanilla and Tekki Minecraft versions run simultaneously, you should also create the Tekkit script from above.
------------------

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:21:24Z

Sc4s2cg: /* Tekkit with McMyAdmin */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

=Tekkit with McMyAdmin=
------------------
Please note that this section was written before McMyAdmin had an option for Tekkit. To make vanilla and Tekki Minecraft versions run simultaneously, you should install Tekkit in the following manner:

*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|nohup ./start.sh}}
------------------

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:17:29Z

Sc4s2cg: /* Installing the Tekkit Server */ Revised instructions to reflect latest McMyAdmin feature

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. Parts of the instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Do not start the Minecraft server upon installation of McMyAdmin.
*Logon to McMyAdmin, go to Configuration, Server Settings, and select Tekkit as the Server Type.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|apt-get install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}

Upon starting of the Minecraft server from the McMyAdmin portal, the Tekkit server will be started instead. Building the world and installing the mods and plugins will take a while (around 5-10 minutes), so make sure to give McMyAdmin sufficient time to finish.

The default port is 25565. This may be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:11:33Z

Sc4s2cg: /* Get and install McMyAdmin */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following to start McMyAdmin. The nohup command will allow you quit the terminal without stopping McMyAdmin server.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else. The McMyAdmin server needs to be rebooted after the password is changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:04:49Z

Sc4s2cg: /* Install dependencies */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

==Get and install McMyAdmin==
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:04:21Z

Sc4s2cg: /* Installing McMyAdmin */

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

==Install dependencies==
*Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-10-25T07:03:58Z

Sc4s2cg: Updated instructions, previous links did not work

Note: Below instructions are for Ubuntu. Fedora users must replace all "apt-get"s with "yum"s. So:

{{Code|apt-get install mono-basic}}

becomes

{{Code|yum install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

* Install dependencies
**Instructions taken from [http://www.youtube.com/watch?feature=player_embedded&v=dtcDTb3XyTY this very helpful YouTube video].
Mono:
{{Code|apt-get install libmono-system-web2.0-cil libmono-i18n2.0-cil}}

Java:
Copy the link to the appropriate Java version from [http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html here]

{{Code| wget [YOURLINKHERE.tar.gz]
tar -xvf jdk-7-linux-xxx.tar.gz
mkdir /usr/lib/jvm/
mv ./jdk1.7.0 /usr/lib/jvm/jdk1.7.0
sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.7.0/bin/java" 1
sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.7.0/bin/javac" 1
sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.7.0/bin/javaws" 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws}}

Check Java version, it should be something like:

{{Code| java -version
It should Reply
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode)}}

* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

Installing HDA on HP Mediasmart Server

2012-10-25T05:49:11Z

Sc4s2cg: Added link to MediaSmart server wiki page

Installing your HDA on an old [http://en.wikipedia.org/wiki/HP_MediaSmart_Server HP MediaSmart server], previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* [http://www.ubuntu.com/download/server Ubuntu Server 12.04 LTS], not the desktop version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-25T05:41:02Z

Sc4s2cg:

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* [http://www.ubuntu.com/download/server Ubuntu Server 12.04 LTS], not the desktop version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-25T05:39:39Z

Sc4s2cg:

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-25T05:32:17Z

Sc4s2cg:

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server. [http://www.mediasmartserver.net/wiki/index.php/HP_MediaSmart_Server_Specification This] page provides hardware specifications to compare with any preexisting PC setup.
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-25T05:28:41Z

Sc4s2cg: /* General Troubleshooting */ Added new question

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Q: ''The MediaSmart server is falshing red and blue when booting''

A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.

Installing HDA on HP Mediasmart Server

2012-10-25T05:13:51Z

Sc4s2cg: Formatting

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

* An HP MediaSmart server
* An extra PC
* A spare hard drive
* An existing network
* An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
* Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

2. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

3. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T05:11:38Z

Sc4s2cg: /* Moving the Hardrive */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

====Troubleshooting====

Q: ''Only one line shows up in step 3, and the MAC address is that of my old PC.''

A: If there is no second hardware address, we will have to add the MediaSmart server's network drive to eth0. Do the following:

Check what eth1's HWaddr is set to. Copy this information.

{{Code|ifconfig C}}

Edit the 70-persistent-net.rules file:

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

Comment out the line with the mac address that was copied down in the previous step, and add the following line (repacing "55:55:55:55:55:55" with the MediaSmart server's address):

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="55:55:55:55:55:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T05:07:50Z

Sc4s2cg: /* Troubleshooting */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T05:06:55Z

Sc4s2cg: /* Transplanting an existing Amahi server */ Added details after I followed through the steps on my own server

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Note the IP address of your HDA. This can typically be found by connecting to the router and seeing what IP is assigned, or checking your [https://www.amahi.org/users Amahi Control Panel].

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.

2. Use [[Key-based SSH Logins With Putty|Putty]] to SSH into the previously noted IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth0"

So above, we commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:39:30Z

Sc4s2cg: /* Moving the Hardrive */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well. Plug them in to any slot, except for slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:38:39Z

Sc4s2cg: /* Preparing the HDA */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

2. Save using ctrl+x, and hitting "y" to confirm

3. Note the hardware address of the network card:

{{Code|ifconfig}}

4. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:36:18Z

Sc4s2cg: /* Preparing the HDA */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Unmount and then, after turning off the server, physically disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive. Turn the server back on again.

{{Code|umount -a}

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:31:57Z

Sc4s2cg: /* Preparing the HDA */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Unmount and then, after turning off the server, physically disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive. Turn the server back on again.

{{Code|umount /var/hda/files/drives/sdb1/}}

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:29:47Z

Sc4s2cg:

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server

- An extra PC

- A spare hard drive

- An existing network

- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]

- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:27:56Z

Sc4s2cg: /* Troubleshooting */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''

A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:27:35Z

Sc4s2cg:

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

==Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''
A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

Installing HDA on HP Mediasmart Server

2012-10-25T04:26:36Z

Sc4s2cg: Added troubleshooting

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

==Troubleshooting==

Q: ''The MediaSmart server's health light is flashing, it is a bluish color''
A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

Installing HDA on HP Mediasmart Server

2012-10-25T04:21:19Z

Sc4s2cg: /* Transplanting an existing Amahi server */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server, installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

Installing HDA on HP Mediasmart Server

2012-10-25T04:20:07Z

Sc4s2cg: /* Installing Ubuntu */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current Amahi server from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

Installing HDA on HP Mediasmart Server

2012-10-25T04:19:54Z

Sc4s2cg: /* Installing Ubuntu */ formatting

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install ''Ubuntu 12.04, the server version''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current Amahi server from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

Installing HDA on HP Mediasmart Server

2012-10-25T04:19:35Z

Sc4s2cg: /* Installing Ubuntu */

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install **Ubuntu 12.04, the server version**. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current Amahi server from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

Installing HDA on HP Mediasmart Server

2012-10-25T04:18:30Z

Sc4s2cg: /* Transplanting an existing Amahi server */ Details

Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC.

The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:

- An HP MediaSmart server
- An extra PC
- A spare hard drive
- An existing network
- An SSH solution, like [[Key-based SSH Logins With Putty|Putty]]
- Ubuntu 12.04, the server version

==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install Ubuntu 12.04, the server version. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:

{{Code|sudo apt-get install openssh-server}}

5. Verify that the SSH is working by connecting with [Key-based SSH Logins With Putty|Putty]. If the SSH is not enabled, enable it:

{{Code|sudo update-rc.d ssh defaults}}

6. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

7. Save using ctrl+x, and hitting "y" to confirm

8. Note the hardware address of the network card:

{{Code|ifconfig}}

9. Shutdown the PC:

{{Code|sudo shutdown now -h}}

===Installing Amahi===
1. Move the hard drive to the MediaSmart server's slot 1, turn on the server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. [http://docs.amahi.org/ubuntu-12.html Install Amahi]

===Modifying Ubuntu for Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

12. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

13. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

You should now be able to access your HDA as a share and as the http://hda link. You can [Install VNC server on Ubuntu Server 12.04|install a VNC server] to connect to the HDA using a graphical interface.

==Transplanting an existing Amahi server==
Here I will present how I transplanted my current Amahi server from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.

===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out the [[Reconnect existing Greyhole storage pool]] page. This will allow you to disconnect the data drives, and only risk the OS drive.

2. Change the interfaces file to reflect eth1, not eth0:

{{Code|sudo nano /etc/network/interfaces}}

auto eth1
iface eth1 inet dhcp

3. Save using ctrl+x, and hitting "y" to confirm

4. Note the hardware address of the network card:

{{Code|ifconfig}}

5. Shutdown the server:

{{Code|sudo shutdown now -h}}

===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. Turn on the MediaSmart server.

2. Check your router for the server's IP address, use [[Key-based SSH Logins With Putty|Putty]] to SSH into that IP address.

3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).

{{Code|sudo nano /etc/udev/rules.d/70-persistent-net.rules}}

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1"

So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.

4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.

{{Code|sudo nano /etc/network/interfaces}}

5. Finally, reboot your HDA:

{{Code|sudo reboot now -h}}

===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.

Installing HDA on HP Mediasmart Server

2012-10-25T04:17:51Z

Sc4s2cg: Added how to transplant an existing HDA to the MediaSmart server

Installing HDA on HP Mediasmart Server

2012-10-25T04:09:54Z

Sc4s2cg: /* Transplanting an existing Amahi server */

Installing HDA on HP Mediasmart Server

2012-10-25T04:09:22Z

Sc4s2cg:

Installing HDA on HP Mediasmart Server

2012-10-25T04:04:39Z

Sc4s2cg: /* Modifying Ubuntu for Amahi */ Just correcting formatting for the past couple edits

Installing HDA on HP Mediasmart Server

2012-10-25T04:04:06Z

Sc4s2cg:

Installing HDA on HP Mediasmart Server

2012-10-25T04:03:29Z

Sc4s2cg: /* Installing Amahi */

Installing HDA on HP Mediasmart Server

2012-10-25T04:02:02Z

Sc4s2cg: Created page with "Installing your HDA on an old MediaSmart server, previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended fo..."

McMyAdmin

2012-08-01T17:42:38Z

Sc4s2cg:

Note: Below instructions are for Fedora. Ubuntu users replace all "yum"s with "apt-get"s. So:

{{Code|yum install mono-basic}}

becomes

{{Code|apt-get install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

* Install dependencies
{{Code|yum install mono-basic
yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin-1}}
* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar
{{Code|cd /var/hda/web-apps/mcmyadmin/tekkit/
mv Tekkit.jar craftbukkit.jar}}

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
mv Tekkit.jar craftbukkit.jar}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-07-31T21:31:25Z

Sc4s2cg: Switched sh to java

Note: Below instructions are for Fedora. Ubuntu users replace all "yum"s with "apt-get"s. So:

{{Code|yum install mono-basic}}

becomes

{{Code|apt-get install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

* Install dependencies
{{Code|yum install mono-basic
yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin-1}}
* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin. I used the GUI here and am unfamiliar with the terminal commands.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
RENAME command}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-07-31T21:30:16Z

Sc4s2cg: Switched sh to java

Note: Below instructions are for Fedora. Ubuntu users replace all "yum"s with "apt-get"s. So:

{{Code|yum install mono-basic}}

becomes

{{Code|apt-get install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

* Install dependencies
{{Code|yum install mono-basic
yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin-1}}
* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
java -Xmx 1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin. I used the GUI here and am unfamiliar with the terminal commands.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
RENAME command}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf}}
Change webserver.port=8080 (line 71) to webserver.port=8081 
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665 
To save do ctrl+x, y (to confirm save), and enter
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties}}
Change server-port 25565 (line 8) to server-port 25665 
To save do ctrl+x, y (to confirm save)
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{link|http://hda:8081}}
* For the Vanilla McMyAdmin:
{{Link|http://hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Link|http://(hda IP):25665}}
* For the Vanilla server:
{{Link|http://(hda IP):25565}}

[[Category:Apps]]

Install VNC server on Ubuntu Server 12.04

2012-07-16T04:20:49Z

Sc4s2cg:

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}

=Method 1=

Install vncServer in Ububtu 12.04 server to create a virtual desktop on another computer

These are the instructions for installing vncserver on Ubuntu 12.04 server edition. They may also work on Desktop, but I haven't tested them on it.

First install ubuntu 12.04 server

Install Amahi using the instructions provided elsewhere on the wiki.

After reboot go to your HDA and login, then go to apps and install OpenSSH and webmin using the links in your HDA.

Reboot

{{Code|Code = sudo reboot now -h}}

From here on I used vim but you can use any editor you are comfortable with just replace vim with your choice.

A quick and short tutorial on vim:

Move the cursor to where you want to edit then press i
Edit as needed, when finished press esc then :wq to save your changes
If you make a mistake press :q! you exit without saving changes, then start again.

A cheat sheet for vim commands can be found here:

http://www.tuxfiles.org/linuxhelp/vimcheat.html

Now go to another machine, I used windows 7, and download putty.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)

From here on it will be all copy and paste in putty. (makes it easy)

Start putty

In Host Name (or IP address) enter the static ip address of your server, you can find it in your control panel on Amahi.org. For example: 192.168.1.55

DO NOT enter http://

Leave the Port at 22

[[File:PUTTY1.gif]]

If you want you can save it for easier later use by adding a name in Saved Sessions and clicking Save

Now click Yes

A terminal will open and another window asking you to confirm the server click okay

[[File:PUTTY2.gif]]

Enter your ubuntu username and password when asked

[[File:PUTTY3.jpg]]

You will be connected to your server.

all the following commands can be copied and pasted into putty with a simple right click.

Copy and paste

{{Code|Code = sudo apt-get update}}

when complete

{{Code|Code = sudo aptitude safe-upgrade}}

reboot server type

{{Code|Code = sudo reboot now -h}}

A: Install Gnome basic desktop.

log in with putty again from your windows machine.

I installed the server version of Ubuntu, so to be able to have a desk top when I log into vnc I need to install a few things in Ubuntu.

First off we need to install the Gnome components for our virtual desktop. Type or copy and paste:

{{Code|Code = sudo apt-get install gnome-core}}

when prompted type Y and then press Enter. This will install the gnome desktop components.

Reboot

{{Code|Code = sudo reboot now -h}}

To keep the desktop and login window from opening in Ubuntu everytime it starts we want to mask out the few lines which start the service.

{{Code|Code = sudo vim /etc/init/gdm.conf}}

The first few lines of the script should look like this once you've edited it:
{{Code|Code =

# gdm - GNOME Display Manager
#
# The display manager service manages the X servers running on the
# system, providing login and auto-login services

description "GNOME Display Manager"
author "William Jon McCann <mccann@jhu.edu>"

#start on ((filesystem
# and runlevel [!06]
# and started dbus
# and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
# or stopped udev-fallback-graphics))
# or runlevel PREVLEVEL=S)

stop on runlevel [016]

emits login-session-start

}}

esc :wq to save the changes or :q! to start over. Now the desktop and login won't start in Ubuntu.

NOTE: This only installs a basic desktop, if you want to be able to use programs from your virtual desktop, network manager, media players, office, etc, they will need to be installed after vnc server is installed.

Reboot

{{Code|Code = sudo reboot now -h}}

B: We need to install VNC server to be able to interact with the gnome components for the desktop.

{{Code|Code = sudo apt-get install vnc4server}}

When prompted type Y and press Enter. This will install VNC Server which is required for running a virtual desktop on another machine.

Next type:

{{Code|Code = vncserver}}

You'll then be prompted to create and verify a new password.

We now need to kill the session we just created and make change the startup script for VNCServer to make it work properly.

So, type the following command to kill the session:

{{Code|Code = vncserver -kill :1}}

Now type the following command to open up the file we need to edit:

{{Code|Code = sudo vim .vnc/xstartup}}

Change it to look like this:

{{Code|Code =

#!/bin/sh

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
#exec /etc/X11/xinit/xinitrc
gnome-session --session=gnome-classic &

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
#x-terminal-emulator -geometry 1280x1024+10+10 -ls -title "$VNCDESKTOP Desktop" &
#x-window-manager &
}}

When you're done editing the file press the Esc key once and type :wq

This should save the changes and bring you back to the command line. If you make a mistake editing the file then issue :q! instead of :wq to abort your changes.

Next type the following command to create the VNC Session once more:

{{Code|Code = vncserver -geometry 1680x1050}}

where 1280x1024 is the resolution of your DESKTOP COMPUTER.

Download and install TightVNC onto your desktop computer.

http://www.tightvnc.com/download.html

When you launch it type your hda server name followed by a colon and the number 1 (this is the name you gave it when you installed Ubuntu)for example: Ubuntu-1204:1

[[File:vnc.jpg]]

Or use it's static ip address and :1 eg: 192.168.1.55:1 in the VNCServer box.

[[File:vnc1.jpg]]

Then click Connect, enter the password you created when you typed after installing vncserver.

[[File:vnc2.jpg]]

You now see the desktop screen.

[[File:vnc3.jpg]]

________________________

C: Write a script to launch VNC

A script is basically a file containing a list of commands which
will be executed each time you run it. I put all my scripts in a
directory below my "home" folder in a folder called scripts.

So, from a Putty session:

{{Code|Code = cd /home/xxxx}}

where xxxx is your Ubuntu username. This command switches us into that directory.

Next we'll create a folder called MyScripts below your home folder. So type:

{{Code|Code = mkdir scripts}}

Switch into the folder we've just created type:

{{Code|Code = cd scripts}}

Next type:

{{Code|Code = vim StartVNC.sh}}

This will create a new file called StartVNC.sh and open it for editing.

Press the i key once and copy and paste the following contents:

{{Code|Code =

#!/bin/sh
echo "JOB RUN AT $(date)"
echo "============================"
echo ""
/usr/bin/vncserver -geometry 1680x1050

}}

NOTE: change the 1680x1050 to match the screen resolution of your Desktop computer

Press the ESC key once and type :wq and press Enter to save.

Next we need to make the file executable so, assuming you called your script StartVNC.sh then you'd type:

{{Code|Code = chmod a+x StartVNC.sh}}

Test the script by typing the following:

{{Code|Code = vncserver -kill :1}}

To make sure vncserver isn't running, then:

{{Code|Code = ./StartVNC.sh}}

A new vnc session should start.

D: Create a cron job in webmin to run the script on boot

Stop vncserver

{{Code|Code = vncserver -kill :1}}

Now open your browser and go to your HDA and click on the webmin app you already installed, click continue to this website at the cert warning.

[[File:webmin1.jpg]]

Enter user and password as required.

[[File:webmin2.jpg]]

Within Webmin click on System and then Scheduled Cron Jobs in the left column. Then click the Create a new scheduled cron job option at the top of the screen that opens.

Click the button next to the Execute cron job as and choose the username you created when you installed Ubuntu. Hint: your username appears in a Putty/Terminal session prompt. eg. yourusernameappearshere@Myhdaserver.

Type or paste the name of your script including the full path

{{Code|Code = /home/xxxx/scripts/StartVNC.sh >/dev/null}}

into the Command box, replacing xxxx with your own usernam. The ">/dev/null" parameter will discard any output the script may produce.

Enter a suitable description in the Description field.

In the When to Execute - Simple schedule drop-down list choose When system boots then click the Create button at the bottom of the screen.

It should look like this:

[[File:webmin3.jpg]]

First test that you've set the job up correctly within Webmin. You can do this by clicking on the job you've just created from the long list of cron jobs (not checking the box but clicking on the name). In the new window that opens click the Run Now button at the bottom of the screen. You should see a message similar to the one you saw when you tested it from a Putty/Terminal session.

Now let's check the script works on boot. So from the System -> Bootup and Shutdown menu within Webmin scroll down to the bottom of the screen and click the Reboot System button. Alternatively type

{{Code|Code = sudo reboot now -h}}

in a Putty/Terminal session.

After reboot go to your Windows machin and open Tight VNC Viewer and connect to your ubuntu virtual desktop. VNC Server now starts automatically on boot.

That's it you should now have vnc server start on boot and a virtual desktop for your server on another machine.

Most of this information was obtained from: www.havetheknowhow.com.

= Alternate Method=
This is just what I found on how to install a VNC for Ubuntu 12.04LTC after figuring out that TigerVNC (the above methods) do not work for Ubuntu. The method is copied from [http://coddswallop.wordpress.com/2012/05/09/ubuntu-12-04-precise-pangolin-complete-vnc-server-setup/ here]. This will result in the gnome GUI, not Unity.

* First we need to update our repositories and install gnome.

{{Code|sudo apt-get update
sudo apt-get install gnome-core gnome-session-fallback}}

* Next we install VNC4Server. Follow the instructions.

{{Code|sudo apt-get install vnc4server}}

* We need to test the VNC, and then close the session. In the process we are prompted for a password to use everytime we try to connect using our VNC client.

{{Code|vncserver
vncserver -kill :1}}

* We open the startup file that we need to edit to make gnome show up in the VNC, and not just a terminal:

{{Code|cp .vnc/xstartup .vnc/xstartup.bak
nano .vnc/xstartup}}

* We edit the file to uncomment the second line, and add "gnome-session -session=gnome-classic &". So it will look like this:

{{Text|Text=
<nowiki>#</nowiki>!/bin/sh

<nowiki>#</nowiki> Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
<nowiki>#</nowiki>exec /etc/X11/xinit/xinitrc
gnome-session –session=gnome-classic &

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
<nowiki>#</nowiki>x-terminal-emulator -geometry 80×24+10+10 -ls -title “$VNCDESKTOP Desktop” &
<nowiki>#</nowiki>x-window-manager &
}}
* And finally we quit nano and save the file.
ctrl + x
y (for confirmation that yes, we do want the file to be overwritten with the new information)}}
* To start the VNC just type the following into a terminal (using something like [[Key-based SSH Logins With Putty|Putty]]. This will start a new VNC session.
{{Code|vncserver}}

VNC

2012-07-16T04:18:32Z

Sc4s2cg: Added link to Ubuntu VNC page

<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NOTE: there is now a one-click [http://www.amahi.org/apps/vnc VNC App]'''
</div>

= Using VNC to use a remote desktop in the HDA =

Using [http://realvnc.com/ VNC] is useful if:

* You would like a Linux desktop to the HDA remotely
* You run your HDA headless (no monitor) and like to still use a desktop in it
* You would like to use a GUI to configure printer(s) or have a scanner or other device that requires a desktop program to configure and the machine is headless

= What you need =

* A server
* A client

= Client: Installation =

Download the client software and install:

* Windows: [http://realvnc.com RealVNC], [http://www.uvnc.com UltraVNC], [http://www.tightvnc.com TightVNC]
* MAC: [http://sourceforge.net/projects/chicken/ Chicken], [http://cotvnc.sourceforge.net/ Chicken of the VNC] (do not use internal vnc client as there are some issues)
* For Linux, you have the vncviewer package, available in most, if not all distros. For Fedora 12, do the following as [[Open_Terminal_as_root|'''root''']] user:
yum -y install tigervnc

= Server Installation =

There are various ways to get the server going in your HDA. All of them require the server software.
# [http://www.amahi.org/apps/VNC VNC]: one-click install
# Manually as described below (notes may require some revision)

=== Manual Install ===
* As root, install the server:

yum -y install tigervnc-server

== Method 1 ==
* Open a terminal, become root and install the VNC server (tigervnc-server) as stated in the Manual Install section.
When the install has completed, press ctrl-D to end the root session. Leave the terminal open, or open one now.

*The following commands are entered as '''User'''.

* Type vncpasswd and press enter.
The system will prompt you for a password. Type a password and press the enter key.
The system will prompt you to verify the password. Type the password a second time and press the enter key.

* Type vncserver and press the enter key. The system will create the configuration files. You should see output similar to this:
xauth: creating new authority file /home/user/.xauthority
New 'host.localdomain:1 (user)' desktop is host.localdomain:1
Creating default startup script /home/user/.vnc/xstartup
Starting applications specified in /home/user/.xauthority
Log file is /home/user/.vnc/host.localdomain:1.log

* You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "user" is shown, you need to enter your user name.

* Type nano /home/user/.vnc/xstartup and press the enter key. Nano will open the file.
Find the following line:
twm &
Change that line to read:
exec gnome-session &
This change will open the VNC display with a Gnome desktop, even if the server is starting in Init 3 by default.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

*The following commands are entered as '''Root'''.

* Type su and press the enter key followed by the root password

You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "username" is shown, you need to enter your user name.

* Type nano /etc/sysconfig/vncservers and press the enter key. Nano will open the file.
Find the following lines:
'#' VNCSERVERS="1:username"
'#' VNCSERVERARGS[1]="-geometry 800x600 -nolisten tcp -localhost"

* Uncomment both lines by removing the # at the beginning of the lines.
Edit the lines so they appear as follows:
VNCSERVERS="1:username"
VNCSERVERARGS[1]="-geometry 1024x768 -nolisten tcp"
Enter your username in place of "username". After "geometry", you can enter any resolution you desire. You can come back and change this if necessary.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

* Finally, type chkconfig vncserver on and press the enter key. This will make the VNC server start when the computer starts.

* Press ctrl-D to end the root session, and then press ctrl-D again to close the terminal.

* That's it - Run your VNC Client and enter hda:1 as the host/IP address. You should now see your HDA Desktop screen.
*If you are interested in more security for your VNC connection, check the link listed below under "General Instructions"

* Repeat the configuration for each user you wish to be able to connect via VNC.
* Note you can have displays for users 1-9 and each will connect to their VNC session at port 590n (some VNC clients 'know' the 590 part and only have you enter n). Make certain that you have forwarded the correct port(s), or the range 5901 through 5909.
* Add -localhost to options if you are connecting through a ssh tunnel or only locally. This adds some security.

== Method 2 ==
* To start the server in your HDA, you need install tigervnc-server rpm package:
* From the '''root''' user:
yum -y install xinetd
chkconfig vncserver off
service vncserver stop
* Create /etc/gdm/custom.conf file and add the following:
#GDM configuration storage
[xdmcp]
Enable=true
[chooser]
[security]
DisallowTCP=false
[debug]
* Create /etc/xinetd.d/vnc1024 file and add the following (you can change the screen resolution by changing the geometry setting):
service vnc1024
{
disable = no
socket_type = stream
protocol = tcp
group = tty
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024×768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none
}
* Edit /etc/services and comment out the two lines as listed below:
#vnc-server 5900/tcp # VNC Server
#vnc-server 5900/udp # VNC Server
* Add this line below the two lines you commented out and save the changes:
vnc1024 5900/tcp # VNC and GDM
* Now restart the xinetd service
service xinetd restart
* Run your VNC Client and enter your HDA IP address for host/IP address. You should now see your HDA Desktop login screen. If you don't see the login screen, a reboot of the HDA may be required. This can be done via the dashboard or by executing the following as '''root''' user:
reboot now

== Method 3 (the cpg method) ==

* Every time the HDA is rebooted, when VNC is needed, ssh to the HDA
* The first time without do:
vncserver -geometry 1550x1100
* After the first time, I type vncs. I have an alias in ~/.bashrc:
alias vncs='vncserver -geometry 1550x1100 &> /dev/null &';

Notes:

* Why that resolution? That fits my monitors with the VNC window and frame enough to not display scrollbars and move around nicely. Change at will!
* It does involve the dreaded CLI.
* Since my HDA does not get rebooted often, this is not a huge problem

== Method 4 (Ubuntu) ==
[http://wiki.amahi.org/index.php/Install_VNC_server_on_Ubuntu_Server_12.04 This] page details two methods for installing a vncserver onto the Ubuntu Server.

= General Instructions =
More detailed instructions are available [http://www.g-loaded.eu/2005/11/10/configure-vnc-server-in-fedora/ here].

= Troubleshooting for Vista =

This helpful page has helped with [http://www.windowsreference.com/internet-explorer/windows-has-blocked-this-software-because-it-cant-verify-the-publisher/ blocking VNC]

= Images for the App =
[[Image:VNC-logo.png]]
[[Image:VNC-sshot.png]]

McMyAdmin

2012-07-16T04:07:11Z

Sc4s2cg:

Note: Below instructions are for Fedora. Ubuntu users replace all "yum"s with "apt-get"s. So:

{{Code|yum install mono-basic}}

becomes

{{Code|apt-get install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

* Install dependencies
{{Code|yum install mono-basic
yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin-1}}
* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed. This can be done on the localhost:8080 link by changing the default password from "admin" to something else.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
sh -Xmx 1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin. I used the GUI here and am unfamiliar with the terminal commands.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
RENAME command}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf
Change webserver.port=8080 (line 71) to webserver.port=8081
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665}}
{{Code|ctrl+x
y (to confirm save)
enter}}
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties
Change server-port 25565 (line 8) to server-port 25665
ctrl+x
y (to confirm save)}}
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{Code|hda:8081}}
* For the Vanilla McMyAdmin:
{{Code|hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Code|(hda IP):25665}}
* For the Vanilla server:
{{Code|(hda IP):25565}}

[[Category:Apps]]

McMyAdmin

2012-07-16T04:03:02Z

Sc4s2cg:

Note: Below instructions are for Fedora. Ubuntu users replace all "yum"s with "apt-get"s. So:

{{Code|yum install mono-basic}}

becomes

{{Code|apt-get install mono-basic}}

=Installing McMyAdmin=

Minecraft server with web-based front end for server management.

* Install dependencies
{{Code|yum install mono-basic
yum install java-1.6.0-openjdk java-1.6.0-openjdk-plugin-1}}
* Get and install McMyAdmin
{{Code|mkdir /var/hda/web-apps/mcmyadmin
wget -P /var/hda/web-apps/mcmyadmin http://www.phonicuk.com/Downloads/McMyAdmin-latest.zip
unzip /var/hda/web-apps/mcmyadmin/McMyAdmin-latest.zip -d /var/hda/web-apps/mcmyadmin/
chown -R apache:users /var/hda/web-apps/mcmyadmin
chmod +x /var/hda/web-apps/mcmyadmin/start.sh}}
* Start McMyAdmin and Minecraft server
{{Code|cd /var/hda/web-apps/mcmyadmin
./start.sh}}
and wait for it to download the latest Minecraft server. Once done stop it with '''<Ctrl-C>''' and run the following.
{{Code|nohup ./start.sh &}}

The web interface runs on port 8080 by default account admin/admin:
{{Link|http://localhost:8080}}

By default the web interface can only be accessed from the machine it is running on. To make it available from another machine the entry passwordmd5 in McMyAdmin.conf.default must be changed.

==Installing the Minecraft Server==

The Minecraft server is included with McMyAdmin and runs on port 25565 by default. After users have properly forwarded ports to the Amahi server Minecraft players will be able to use the HDA URL to connect to the server.

Cronjob will need to be set for autostart on boot. Amahi may also be able to monitor this server to make sure it is running, similar to other services.

==Installing the Tekkit Server==

'''''To logon to a Tekkit server the user must use the [http://www.technicpack.net/launcher/ Technic Launcher] and not the default MineCraft app.'''''

[http://www.technicpack.net/tekkit/ Tekkit] is a collection of Minecraft mods that allows for more advanced gameplay. The purpose of this tutorial is to illustrate the installation of Tekkit on your HDA. All commands below are for the terminal. The instructions are taken from [http://www.youtube.com/watch?v=u8-uGqSyaMo this] fine YouTube video.
*Navigate to the default hda web-apps folder
{{Code|cd /var/hda/web-apps/mcmyadmin}}
*Create a folder for Tekkit and get in the folder:
{{Code|mkdir tekkit
cd tekkit}}
*Download the latest Tekkit server zip file from [http://www.technicpack.net/tekkit/ here]. Replace my link below with your own latest one.
{{Code|wget http://mirror.technicpack.net/files/Tekkit_Server_3.0.4.zip}}
*Extract the zip file with unzip. Replace name of file with your own latest one.
{{Code|yum install unzip
ls
unzip Tekkit_Server_3.0.4.zip}}
*Create startup script for Tekkit. Note that 1500M stands for the number of megabytes of ram you are letting Tekkit use potentially. The 512M stands for the number of megabytes of ram you let Java use at startup.
{{Code|nano start.sh}}

{{Text|Text=#!/bin/sh
sh -Xmx 1500M -Xms512M -jar Tekkit.jar}}
*Give permissions to the script.
{{Code|chmod +x start.sh}}
*Start Tekkit
{{Code|./start.sh}}

The default port is 25565. This will be edited below.

=Tekkit with McMyAdmin=

* Before continuing, you must start Tekkit and stop it after Tekkit has completely loaded. This will create essential files.
{{Code|cd /var/hda/web-apps/tekkit
./start.sh
stop}}
* You must also do the same thing with McMyAdmin
{{Code|cd /var/hda/web-apps/mcmyadmin
mono McMyAdmin.exe
stop}}

For the purposes of this tutorial, it is assumed that both McMyAdmin and Tekkit have been installed and started/stopped as outlined above. We need to copy the Tekkit files into McMyAdmin. I used the GUI here and am unfamiliar with the terminal commands.

* Go into the Tekkit folder, rename Tekkit.jar to craftbukkit.jar

==Tekkit and Minecraft Vanilla Coexisting in McMyAdmin==

* Follow the McMyAdmin tutorial above, except name the McMyAdmin folder "McMA_Vanilla". Replace all "McMyAdmin" with "McMA_Vanilla" as needed.
* Create a folder called MineCraft.
{{Code|mkdir /var/hda/web-apps/MineCraft}}
* Copy (not move) McMA_Vanilla into the MineCraft folder.
{{Code|cp -fr /var/hda/web-apps/McMA_Vanilla /var/hda/web-apps/MineCraft}}
* Rename the original McMA_Vanilla to McMA_Tekkit.
* Move McMA_Tekkit into MineCraft folder.
{{Code|mv /var/hda/web-apps/McMA_Tekkit /var/hda/web-apps/MineCraft}}
* Follow the Tekkit tutorial above.
* Rename the Tekkit.jar file to craftbukkit.jar, AFTER having started and stopped the Tekkit and MineCraft servers at least once as outlined above.
{{Code|cd /var/hda/web-apps/tekkit
RENAME command}}
* Copy the contents of the tekkit folder into the McMA_Tekkit/Minecraft folder, merge and replace all files as needed.
* Delete the now empty tekkit directory
{{Code|rm -fr /var/hda/web-apps/tekkit}}
* Now we must edit the ports so that both McMyAdmin servers can run at the same time:
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
nano /McMyAdmin.conf
Change webserver.port=8080 (line 71) to webserver.port=8081
Change server.address=localhost:25565 (line 152) to server.address=localhost:25665}}
{{Code|ctrl+x
y (to confirm save)
enter}}
* And the same must be done with the MineCraft servers
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit/Minecraft
nano server.properties
Change server-port 25565 (line 8) to server-port 25665
ctrl+x
y (to confirm save)}}
* Start the Tekkit server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Tekkit
mono McMyAdmin.exe}}
* In a new terminal, start the Vanilla server
{{Code|cd /var/hda/web-apps/MineCraft/McMA_Vanilla
mono McMyAdmin.exe}}

=Access McMyAdmin=
* For the Tekkit McMyAdmin:
{{Code|hda:8081}}
* For the Vanilla McMyAdmin:
{{Code|hda:8080}}

=Join MineCraft Server with Client=
* For the Tekkit server:
{{Code|(hda IP):25665}}
* For the Vanilla server:
{{Code|(hda IP):25565}}

[[Category:Apps]]