Need Linux With Occasional MS Office?

My father is a Linux Mint convert over the last three years, and has been running Linux Mint 9 since 2009. Unfortunately he has to use MS Office for some work things, including writing and running macros, so he can’t can’t get away from it completely (it’s for state schools usually, so it should be available in some open format, but I digress). He loathes having to select to boot windows in grub.

Anyway, recently Windows has creaked to (even more of) a crawl on his old tosh satellite, probably infected with something horrible because he rarely boots it and something got in between AVG and Spybot updates. OpenOffice on Mint 9 is getting long in the tooth. He asked me if I could think of another way around the problem that could allow him to be able to get in and out of Windows quickly, cut and paste between Windows and Linux quickly, have a better OpenOffice version and not have to worry much about the infections.

Various solutions were discussed, researched, and discarded. Some of them were:

  • Wine – MS Office is not too clever in any of the bottles yet
  • Crossover office – ditto
  • Full reinstall of Windows XP then Office 2010, then upgrade Linux Mint to 11 – going to be in same situation in x months time when XP grinds to a halt again

After a moment of clarity, we went with: upgrade to Linux Mint 11, install VirtualBox OSE, create a Windows XP VM with Office and take a snapshot, turn off networking on the VM, share a folder on the Linux box with the windows VM, and have Virus monitoring on the Linux box.

This solution gives us the fast switching between OSes; cut and paste (with the VirtualBox add-ins); the latest LibreOffice; and, when the Windows VM gets infected (pretty sure bet, even with networking turned off), rollback to the clean snapshot. Downsides are having to run an instance of Windows and MS Office. Money and sales target ticks for MS.

Here’s what we had to do. First the prep, which mostly took place before the big meetup. If we’d done all of it before, it would have saved us a couple of hours on the day.

  1. Backup /home
  2. Confirm nothing on the Windows partition needing backing up
  3. Torrent the Mint ISOs and select required version (we checked LXDE and Gnome standard. My father still prefers Gnome so we went with that)
  4. Find the Windows XP Pro install disk that came with your machine originally (you did get one, didn’t you?)
  5. Find the Windows licence code on the bottom or side of your machine
  6. Find your Office DVD and licence code
  7. Download Windows Service Pack 3

For the actual day I went a little further, just to make things more bearable:

  1. Persuade lovely wife to prepare and cook a topside of beef with all trimmings
  2. Get in sufficient wine and cheese for the day of the install

On the day, here’s the actions we went through:

  1. Confirm /home backup is ballpark. du -hs /home; du -hs /media/backupDisk/home
  2. Fire up Linux Mint 11 Live DVD and install Linux Mint 11. We have a diddy 60GB HDD so partitions were:
    • 14GB primary, mount point / – system, etc (too big, but playing for the long haul)
    • 2GB swap – logical, at end of disk
    • Rest logical (44GB-ish), mount point /home
  3. Restore /home from the backup.
  4. In Software Manager install
    • VirtualBox OSE
    • VirtualBox Add-ins ISO image
  5. In VirtualBox:
    1. create a new VM for Windows XP. Give a dynamic growth to 15GB. More than enough, but you have a lot of upgrading and installing to do and nothing is worse than a windows machine with a rammed full system disk
    2. Install Windows XP Pro (don’t even think about XP Home). Hope you have SP2 at least
    3. Install Windows Service Pack 3
    4. Install Windows Updates – there were 64 for us, the 48th was IE 8 and needed questions answering, so don’t walk away
    5. Install MS Office 2010
    6. Flag the network adapter with “cable unplugged”
    7. Start Word and fill in all the author blurb
    8. Mount a shared folder in the linux /home/username/ area (with AV protection on it). Make it permanent mount.
    9. Full screen the VM and take a snapshot
    10. Give yourself a pat on the back (and swing your pants)

    It took a long, long time, most of it getting Windows installed right, but we won’t have to do it again (I don’t think). Mint will look after itself largely, with upgrades being pretty simple now. If windows goes slow, my father can just rollback to the pristine VM image.

    Other things we wanted to do but didn’t have time:

    1. Setup sshd for remote admin access
    2. Setup LVM so we grow the disk space onto a PCMCIA card HDD at some point
    3. Setup dropbox for remote doc backups – need to investigate as last I heard dropbox had been compromised, not sure what resolution was.
    4. Setup Picasa for picture admin and remote backup
    5. Drink Bowmore

Getting MSSQL Command Line Access from ISQL on Ubuntu

Install freetds
sudo apt-get install freetds-bin

Check it works:
fsql -S -U

See how to use it (it pretty much matches isql and bcp).
man fisql
man freebcp

Engineer Victory Dance (the hard work was done the freetds posse and all those lovely linux peeps, but dance anyway, required action).

Weather Check

If you have a linux OS the bash shell script below will tell you most recent temp, windspeed, direction, and rainfall at Everton, Sandy, and Biggleswade from local weather stations using weatherunderground. I crontab it, piping the results to mail -s ‘Current weather’


function checkComponent() {

       curl -s $aurl | tail -3 | tr '\n' ',' | awk -F, ' { print "NAME@ " (5/9)*($2-32) "C dp " (5/9)*($3-32) "C " $5 "@" $8 "mph " $92 "CurrentRain " $10 "in DailyRain " $13 "in\n" } ' | sed "s:NAME:${name}:" >> tempweather

checkComponent IENGLAND82 Everton
checkComponent IBEDSBIG1 Biggles
checkComponent I90580822 Sandy

cat tempweather
rm tempweather