Posts tagged ‘Ubuntu 12.04’
As a general rule, I always make a full backup of all personal folders on my home Ubuntu 12.04 machine at least every two weeks. I don’t use scheduled backups. Backup for a private machine is just a thing I like to do manually, on a lazy Saturday morning with my first cup of coffee. I use Deja-Dup, and backup to a local USB device, with sufficient free space. Normally, I just have to plug in the device, and then start the “all personal folders” backup with this terminal command: sudo deja-dup-preferences. I then backup to this NTFS formatted disk (name: TOSHIBA EXT). Note that the default name contains a space. But why NTFS? Simply because I never bothered reformatting it as ext3, or whatever Linux file system. Until now, my Ubuntu 12.04 machine had always detected the USB disk, so why should I care?
This morning however, when plugging in the USB disk, it was not recognized by the operating system. Kernel problem? Hardware failure? I don’t know, and frankly, I don’t care too much…as long as I have my Saturday morning coffee and my weekly backup. I guess I’ll just have to wait for an Ubuntu update, to have the USB disk get detected again on my primary machine. And if really it’s a hardware problem, well, then let’s already look for a cheap alternative, and use it straightaway. And be creative, on a Saturday morning with a couple of coffees.
I also use a MacBook Air, that came with my new job as system administrator. I had already noticed that the backup USB disk was perfectly detected by this MacBook Air. So basically, I would have my backup, if I was able to access the USB disk, over my private network. Now I had two challenges:
– allow this MacBook to be accessible through SSH. Deja-Dup can use an SSH session for backup ;
– allow the NTFS disk to be read-writable, when attached to the MacBook. By default, NTFS devices are read-only when attached to Mac OS X.
Allow SSH on a MacBook is a breeze. Just start System Preferences – and allow SSH – see this print-screen.
Allowing an NTFS formatted USB drive to be read-writable on Mac OS X: well, just have a look at the following example, and create the /etc/fstab file with the following content:
If you want to test it yourself, please notice how to escape the space in the device name: backslash followed by 040.
Plug in the USB disk after creating this file, and you’re off!!! Your USB NTFS formatted disk will be accessible through SSH. And, thus, backup over SSH with Deja-Dup, to a MacBook with an NTFS formatted external disk.
Right now, my backup to the USB device, over SSH to the USB disk is running…
In the meantime I switched from coffee to a fine glass of wine, since I am writing this post in the evening. And off preparing some stamppot boerenkool for, my kids, my wife and me.
This article is a continuation of two previous articles: Ubuntu, Remote Desktop and Windows Remote desktop (1 and 2). It is advised to read those two articles first.
In my previous article, I have explained how to auto-start and auto-pause a VirtualBox VM with Ubuntu. Now let’s see how we can use this feature in a broader context: using a remote desktop solution that enables remote usage of Linux and Windows desktops, from any device, and basically, from anywhere. Anywhere includes access to internal computers from the Internet. For the latter, and with the product that I use for it: a good firewall protection (maybe double), a correctly working DNS, understanding of Network Address Translation and understanding how to harden an SSH server at least with Public Key Authentication are essential. I won’t go into details about accessing an internal desktop from the Internet with the solution explained below. Suffice it to say that I do so. But since security is essential, I won’t publish any details. Numerous articles on the Internet explain items like SSH, alternate SSH ports, Public Key Authentication, Port Redirection, etc.
For remote access within my home network, I use a free ten user version of ThinLinc, which I installed on my HP xw6400 Workstation with Ubuntu 12.04. ThinLinc is a Thin Client solution based on Linux. It has excellent sound and video support. In my home situation, even when accessed over two wireless simple SOHO access points, the sound and video quality of e.g. a complex Youtube movie is still acceptable. In other words: ThinLinc just rocks. One more thing though: I strongly advise to install this software on Ubuntu versions that are supported by ThinLinc, and not to try the software on non-LTSP versions of Ubuntu. Ubuntu 12.04 is supported, according to the documentation.
I won’t go into details about the installation of ThinLinc. An excellent instruction, though of an earlier version than the current one, can also be found on Youtube. It is also very well explained in their online documentation.
By the way, ThinLinc has many, many more possibilities than I use in my home network. I just use a fraction of their numerous options.
Anyway, if you’re interested in trying this solution, take your time to read their online installation documentation first, because for the rest of this article, I assume that the reader is familiar with ThinLinc terminology.
Next, have a look at what you can achieve with their software with their online demo.
Also, first create an Ubuntu test virtual machine to familiarize yourself with the installation procedure. Then next with the knowlegde you gained, proceed to a real life installation.
What I myself remember of the installation, is that it was not difficult. Having already installed an Apache web server (sudo apt-get install apache2) but not the SSH server, the installation procedure corrected this issue by installing all missing pieces directly from the web. In less than half an hour, I had a fully functional ThinLinc server.
After having logged in to the admin web interface, I enabled two profiles, and disabled the rest.
The Unity2D profile allows encrypted remote sessions to Linux machines where the VSM Agent is running. So if the VSM Agent is running on the same machine as the VSM server, the profile chooser will contain an option to connect to exactly the same server. Well, since I have only one physical machine… And that’s already the whole trick for remote sessions to your own Ubuntu machine.
The Windows profile allows encrypted remote sessions to Windows machines where the ThinLinc WTS Tools are installed. Here, the trick is quite simple as well: under Application Servers, just point your default to the Virtualbox VM (with WTS Tools) that is auto-stated at boot time of the Ubuntu host.
The result, when starting a remote Thinlinc session, is the following.
Mind that for this remote desktop example, I use the HTML5 client: no client software on the client device, just a plain and simple (encrypted) HTML page in FireFox. Ready to install clients are available as well.
When clicking on Unity2D, a session is established to the Ubuntu desktop where the ThinLinc software is installed.
And when choosing my Windows Desktop…a session is established to the VirtualBox VM that was auto-started…at boot time of that same Ubuntu Desktop machine.
Oh, and did I already mention that in this way, I am able to print from any device, to the printer that is attached to exactly the same Ubuntu host? Because that is another thing: Thinlinc allows printer redirection as well.
So basically, whether accessing a web page or using the Thinlinc client…off you go with an Open Source solution that allows you to connect to Linux and Windows your computers from any device in your home network!
Learn and have fun!