services shifted to a new VPS in the last several hours.
Hopefully everything's still working. Do get in touch if you find something borked. :)

I've had some interesting exchanges with people who've been sending me connect requests of-late. My usual approach - that I will connect with people 'with whom I have done business, or who I know personally' - tends to result in me fending off unsolicited connection requests from a swathe of people who fit into neither category. Of those, one can usually classify the request as being:

  • A recruiter, looking to recruit me for a role
  • A recruiter, looking for a role for a candidate already on the books
  • A recruiter, looking to expand their network in order to potentially action either of the above at some point in the future
  • A jobseeker, looking to make connections in order to find a role for themselves - and these are often offshore candidates (plenty from India, Pakistan, Bangledesh, Sri Lanka and South East Asia in general)
  • A Sales Manager, Account Manager or Business Development Manager looking to draw attention to their latest innovation that they really want to sell you
  • One of the aforementioned three ultimately trying for the same outcome, but being more subtle about it (playing the long game).
  • Someone else from the Industry, engaging their LION (Linked-In Open Networker) - basically expanding their professional network for as-yet-unqualified reasons (but in my experience many LION types are also sales-and-marketing focused at some level.)

All of the above - except perhaps the job-seeker and maybe the LION type - are looking to ultimately make money from me. Thus all of them are, fundamentally, sales or revenue-driven networkers who are playing off the numbers - if even 1% of connections over the course of a day/month/year engage with me for business, it's worth the relatively small mechanical effort to click 'connect'.

I was amused to see the NZ Police Commissioner claiming "Prevention Approach Pays" as a win.

Whilst I actually give the Police their dues in a general sense - they seem to have done fairly well in terms of the 'usual headaches' that the holiday season would present - any attempt to suggest that the reduced speed tolerance is in any way responsible for significant reductions in road deaths during the holiday period, is something I would object to strenuously.

The Commissioner is relatively brief in his statement regarding the road toll:

Many of you will be as saddened as I was by the number of people killed on our roads during the official holiday period. The 12 deaths were four fewer than last year, but that still means 12 victims and a dozen grieving families too many.

The official holiday period ended last Tuesday, but many thousands of people are still away on leave, and I know our staff will continue working hard to keep people safe on our roads.

But it doesn't take much looking to find the table of holiday road tolls over the last several years.

What is obvious:

  • In the last 5 years, the number of road deaths in this last holiday season runs 3rd-equal with 2010-11
  • 2011-12 had the most, with 19 deaths
  • 2014-15 had the next most, with 16 deaths
  • 2010-11 had one more accident for the same number of deaths. I'm not sure that matters.

Had to scratch my head to find the right tool for the job today - something that I used regularly at SMX but havn't had much need to use since.

The tool was 'vimdiff'. I needed to compare to configuration files (retrieved from two different servers) to understand what difference existed. Whilst 'diff' alone would've done it, I find the output hard to follow. vimdiff worked wonders!

Google hit I used also has some other useful tools:

For posterity.

Honourable mention for icdiff also.

I was inspired to Google after (yet again) getting frustrated by inconsistent user experience in Microsoft Outlook.

Short version; Outlook's trying to act like a professional word processing package when you use 'HTML' format for email creation, and actively using behavior contrary to pretty much every other MUA.
What's new?

I ordinarily enjoy using Outlook as an MUA but it does have a couple of annoying quirks, this is definately one of them. The content of the above link is likely to be useful.

I came across a Reddit Thread recently which included this gem:

From the comments that have been posted on this thread and what I found on the Mozilla forums so far:

1- In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

2- Set browser.newtab.url to about:blank>

3- To disable the callbacks to without enabling the "do not track" feature you need to remove the address from and


So i've now done both of the above and feel much better.

The Reddit page linked to a article talking about Mozilla's new Advertising strategy. I for one don't need a third party tracking what I do when I click on 'new tab' ... ! Interestingly there's also a move to remove browser.newtab.url due to "Abuse" which seems to be in itself, contentious, but it's possible you'll have to use an addon to achieve the above, at least in part, in the near future.

Amazed that even 3 years later, nothing's changed.

... so which sign-in button do I press?

For future reference, the right hand one of the two is the correct one. This is what you get if you click the left one - a screenshot I took >6 months ago:

Of note, Tweets from 2012:

... their whole process has been broken for at least 3 years and hasn't changed.

This years Tweets:

Today at #NetHui I attended a discussion on Disaster Recovery.
Ham radio got a brief mention.
Then later the same day, I get referred to this:

Never underestimate the value that ham radio can bring to communications 'when all else fails'.

Yes i'm still here. I know i'm not really an active Blogger at the moment (my rants have landed more on Facebook and Twitter than anything else) but I am still alive, and still very, very busy.

PS: Linux Conf 2015 was awesome. You might spy me on which will give you an idea of what I got up to. At some point I might even write about it....

Sorry, couple more glitches with the server today. Really need to get on to migrating onto the new hardware I have running in parellel...

However I did find this useful stuff today :-)

Force Reboot :
#echo 1 > /proc/sys/kernel/sysrq
#echo b > /proc/sysrq-trigger
If you want to force shutdown machine try this.
#echo 1 > /proc/sys/kernel/sysrq
#echo o > /proc/sysrq-trigger

Remove comments as required. :)

Syndicate content