15 September 2013

Windows to Linux Migration: A translator’s experience

About two weeks ago I did a full Windows to Linux migration on my translation machine.

"Why would anyone want to do that?" you may ask.

Well, for a bunch of reasons. First of all, support for Windows XP will officially end in six months. In April 2014 Microsoft will send out the last security updates, after which the door will be pretty much open for virus and hackers.

Second and more personal reason, throwing away stuff makes me feel guilty. Planned obsolescence is my bane, because I feel the draw of new & shiny like everybody else, but disposing a fully functional PC would make me feel like an irresponsible child. (Keep in mind that when I *do * must get rid of something to save space in our tiny Tokyo flat, I actually give it away through free ads just to avoid the moral burden of waste...).

Third and last, while Windows 7 should run reasonably well on my system (Athlon 7550 Dual Core 2.5 Ghz) I would be in the uncomfortable situation of being in the lower-end of a system that has already been superseded (one might even say disowned) by Windows 8.

On the other hand... "As far as I'm concerned the latest version, Linux Mint 15, Olivia, is now not merely the best Linux desktop, it's the best desktop operating system of all." "Cinnamon, which is the Mint interface I chose to review (...) is designed for power-users who already know how to use a WIMP-style desktop. A Windows XP or 7 user who's never touched Linux in their life will find Mint Cinnamon far more user-friendly than Metro."

Back in the days, such a comment might have come only from an hardcore Linux fan -probably with that ominous mascot in its signature- Now, it's straight from a review on Zdnet!

Installation

The first part of the installation was pretty smooth: I simply downloaded Linux Mint 15 "Olivia" - Cinnamon (32-bit) (indeed, they DO like over-complicating things over there) and launched the installer from a USB stick.

The installer comes with its own tool for resizing hard disk partitions (read "carving out space from your Windows drive to be used by the new system").

I am confident the tool works fine, but this being my production machine (and having a special 7th sense for picking wrong options in menus), I bought a new 1TB hard disk from Amazon just to be safe. The peace of mind of leaving my old system alone was well worth 50 EUR.

About fifteen minutes later the system was fully installed and ready to go. Well... at least in theory, as my first boot led to a garbled screen! Apparently, my video card (AMD Radeon HD6670) wasn't properly supported by the default drivers. So I had to boot in "compatibility mode" and find a way to fix it. Hopefully, there is a link to a support chat room straight in the main menu. A quick chat with an helpful volunteer, a quick change in the configuration menu and I could finally access my new desktop

Linux Mint 15 boot screen Linux Mint 15 boot screen

The system itself

Using Mint itself was a complete non-event for me. First of all because the interface is very similar to Windows, down to the placement of certain options and settings.

But most importantly, because I was using a lot of open source applications already. Firefox, Thunderbird, Filezilla, VLC... It's hard to feel lost when you get to use the exact same tools, and without even having to download them, since they come pre-installed into the system.

For the few that were missing, like Skype or Dropbox, there is a tool called Software Manager that works pretty much like Google Play or the App Store. You search the application, you glance the reviews, and then you just have to click in order to get it installed right away.

The process is not perfect, for example I had to install Dropbox twice before I could get the contextual menus to work, but it feels solid enough - and knowing that I can instantly access a huge library of free and tested applications of all kinds is definitely a plus.

Mint 15 Software Manager Mint 15 Software Manager

The Elephant in the room

Nope, Linux cannot run Trados, nor memoQ, nor Office. Linux cannot run any Windows application at all. In order to use them, we need a virtualization layer, a software able to bridge between the Windows and Linux world.

The lightest, less intrusive solution was CodeWeavers CrossOver which, for 60 USD, allows applications to run natively in a thoroughly tested platform. Alas, both Trados and memoQ just sort of kinda work with this and that setting and the Moon and Jupiter in that quadrant... and really didn't seem reliable enough for production.

This meant using a real virtualizazion platform, able to run a full Windows system inside Linux. and the first solution I tried was VMware Player. As it wasn't available through the Software Manager, I downloaded it from here, and faced a constant stream of tiny issues. First the installer wouldn't launch, then I couldn't get a link to the application and finally I had to give up because (after much tweaking) I still didn't manage to properly access files. From what I saw it's a great application, maybe even faster than VirtualBox, but the installation process was just too complex for a beginner like me.

VirtualBox

So I ended up using VirtualBox, which is hosted inside the Software Manager/Synaptic/Repository and thus more thoroughly tested.

As I mentioned above, this kind of solution creates a full "virtual" computer via software on which you install Windows. This meant actually popping in the Windows installation disk and wait it to complete but, most importantly, meant that I needed a full Windows license.

In my case it wasn't a problem, because through my previous systems and years I have been accumulation 3/4 different installation disks (they are fairly cheap to buy in Akihabara). This said, they can be bought just as easily online for 50 USD or less.

Luckily, the process was much smoother than with VMWare, the only concerns being the inordinate time Windows XP took to download its 200+ updates (I actually left the system running overnight for it to finish) and a problem with USB devices (which was fixed with a one line command).

At the end of the process I now had a fully functional Windows machine next to my Linux desktop.

Virtualised Windows XP running inside Mint 15 Virtualised Windows XP running inside Mint 15

Much ado about nothing?

One might wonder what's the point of it all if you are still using Windows XP anyway, especially if we consider that virtualization drains quite a lot of CPU and memory. For the first couple of day I wasn't very sure about it myself, but facts proved me wrong.

First of all, the virtual system is very fast: I can boot it and start translating in less than 20 seconds. Better than the real thing. I guess there is some very smart optimization going on, but I think the main reason is how lean the system is.

And that's the second big plus so far. When I had a real Window system, it covered my translation tasks (memoQ, Trados, Xbench, dictionaries...) but also all my daily and communication needs (Thunderbird, Firefox, Skype, Dropbox, music player, Kindle...) Now things are clearly separated: Windows is 100% translation focused, Linux covers the rest. This is clearly helpful for the system itself, but also for me. memoQ is slowly digesting a huge file on Windows? No problem, in the meantime I can do this month's invoices on my Linux desktop. Two PC for the cost of one.

Finally, one might wonder how slower the computer must be compared to before, now that it has to run two systems in parallel. In truth, it's not slower at all, as it's using resources that were wasted.

First of all, I have a dual core CPU but most of the programs I used weren't optimized for that, so the second core sat dormant 90% of the time. On top of that, while I have 4 GB of RAM physically installed, Windows XP was only able to access 3, one GB sitting dormant again. Now, if you consider that the virtual Windows machine takes for itself one core and 1 GB of physical memory, we can substantially say that it runs for "free".

Honestly, I was very doubtful about this virtualization malarkey myself, and I am not yet ready to embrace it enthusiastically, but so far it has been running without a hitch, and with clear benefits to my work. I can't ask for more!

(cover credits)