Recently though The Movie Database plug-in on my OpenELEC installation has become broken and will no longer retrieve movie metadata, posters and fanart.
After troubleshooting the issue a little and waiting to see if it would be fixed I decided to move on and discovered LibreELEC – a fork of OpenELEC.
While I always liked OpenELEC I have to say that LibreELEC has already impressed me more since installing it. In my opinion the GUI and menus are much improved – everything is visually appealing and better organized.
I have encountered two minor issues though:
Close to 200 of the movies that were scraped upon adding their sources have the incorrect year of 1969 as their date. This can be fixed manually by refreshing the meta-data but is still a little annoying.
I created a 2nd profile for kids content and could not see the add network location option when selecting a content source. The fix for me was to toggle the unlock sources switch to on under the view settings.
Installing LibreELEC was very straightforward. While I believe that you can update an existing OpenELEC installation to LibreELEC I opted to simply install LibreELEC over it. If you are starting from scratch with a new Chromebox please refer to the first half of my original blog post here. Otherwise I would recommend an Intel NUC over the Chromebox because of the ease of installation. A NUC can much more easily be re-purposed should the need arise.
To install LibreELEC visit the download page and grab the USB-SD Creator for your PC, Mac or Linux box.
For a Chromebox installation:
Select Generic AMD/Intel/NVIDIA (x86) from the select version drop down menu.
Click the Download button.
Select your USB drive from the drop down menu and then click the Write button.
This will erase your USB drive and create a bootable LibreELEC installation.
From here simply put your USB drive in your Chromebox and boot from USB. To do this press the Escape key on your keyboard while your Chromebox boots and then select option 2 to boot from USB.
Follow the prompts and LibreELEC will very soon be up and running!
Remove your USB drive once LibreELEC is installed.
I wrote this guide in 2014 and now in 2018 I find that the add-ons in OpenELEC for scraping Movies etc no longer work. I now recommend installing LibreELEC instead of OpenELEC. In addition I would now recommend a low end Intel NUC over a Chrombox because of ease of installation. The difference in price between the two is not that great any-more.
There is a lot of great documentation available for installing OpenELEC aka XBMC (now renamed Kodi) on a Chromebox – but I wanted a brief summary of the steps I performed should I need to do it again.
I have been running OpenELEC as my media center of choice for quite a while now on a 7 or 8 year old PC. As that PC just died I needed a replacement – something smaller – and something cheaper! The ChromeBox looked like an ideal choice …
These steps remove ChromeOS and install OpenELEC – so consult the documentation (and do not do this) if you prefer a different configuration! You have been warned! Seriously, read the documentation!
Enormous thanks to Matt DeViller for providing the installation script, documentation and support to the community!
On Ubuntu the hostname is stored in both the /etc/hosts and /etc/hostname files. There are several ways that we can change the hostname in these files.
1. Manually Edit the hostname
We can manually edit these files using a basic text editor like nano:
sudo nano /etc/hosts
sudo nano /etc/hostname
In /etc/hostname simply overwrite the existing hostname with a new one. In /etc/hosts you will find the hostname on the line beginning 127.0.0.1 – overwrite only the hostname with the new one, and then reboot.
2. Use sed to change the hostname
Another way to achieve the same goal is to use the sed command to replace the existing hostname with a new one.
For example, my Ubuntu Server has the default hostname of ‘ubuntu’.
Use the hostname command to check what your hostname is.
With sed we can look for our hostname (in /etc/hosts and /etc/hostname) and then replace it with the desired new-hostname:
sudo sed -i 's/ubuntu/new-hostname/g' /etc/hosts
sudo sed -i 's/ubuntu/new-hostname/g' /etc/hostname
3. Write a Bash Script
It’s always handy to have a script to do things – so here is a quick bash script that I put together that uses sed to change the hostname and then reboot:
#Assign existing hostname to $hostn
#Display existing hostname
echo "Existing hostname is $hostn"
#Ask for new hostname $newhost
echo "Enter new hostname: "
#change hostname in /etc/hosts & /etc/hostname
sudo sed -i "s/$hostn/$newhost/g" /etc/hosts
sudo sed -i "s/$hostn/$newhost/g" /etc/hostname
#display new hostname
echo "Your new hostname is $newhost"
#Press a key to reboot
read -s -n 1 -p "Press any key to reboot"
I’ve lost count of the number of times that I have installed Ubuntu Server on my VMware vSphere box – so I finally looked in to performing an unattended install.
I could have setup DHCP and TFTP servers and done PXE boot from images over the network – but I wanted to work on something quicker than that (and I don’t have that much spare RAM on my vSphere box as it is).
So I settled on re-mastering an Ubuntu Server .iso image. The result is an unattended install, except for the initial boot screen (where I need to select a minimal virtual machine installation anyway).
The following steps were performed on Ubuntu Desktop.
The -r switch copies directories recursively and -T specifies no (singular) target directory.
Now we have a copy of our Ubuntu .iso to work on in /opt/serveriso – but we need to make these files writable:
sudo chmod -R 777 /opt/serveriso/
With this preparation done we can start customizing things.
If we look at the isolinux/langlist file we see all the supported languages listed that Ubuntu supports (in an abbreviated format):
I am only interested in an English install so I am going to overwrite the contents of isolinux/langlist with the single abbreviation for English, which is “en”.
echo en >isolinux/langlist
This stops the language selection menu from appearing during installation.
The next step of the process is to create a kickstart file – this will provide the server install with the answers to the various questions asked during installation, such as timezone, username, password, partition structure and so on.
Install Kickstart Configurator:
sudo apt-get install system-config-kickstart
Click the Dash button and type kickstart and then click on the kickstart application.
Obviously you should customize your settings as you see fit – I have provided mine for reference.
Click File, Save File and save the kickstart file ks.cfg to /opt/serveriso.
While using the Kickstart Configurator you may have noticed that the Package Selection screen did not work. Fortunately we can manually edit the ks.cfg file so that the packages that we want are installed during Ubuntu Server installation.
At the end of ks.cfg add %packages and then list the packages that you want installed. I chose to install nano, openssh-server and open-vm-tools:
The WordPress Metro App is a good looking tool for posting to WordPress. It has a nice clean minimalist design which is unfortunately only matched by the lack of features.
The app only allows for basic text features such as bold, italic and strike – basic lists – and then text alignment. Add hyperlinks and the ability to add locally stored images and that is it.
I was hoping for more – such as the ability to add images that are stored on wordpress.com, add tags and categories and so on. I cannot switch to HTML view or even save a draft.
There are so many features that I use that are missing that this will probably be the last time that I ever use the WordPress Metro App – which is a shame. I hope that there is some further development for this app as otherwise it is quite nice to use.