May 312017
 

The title is not meant to be taken seriously except as a poke of fun at the notion that border between England and Scotland is set in stone and has always been there. It is essentially an excuse to counteract some of the anti-English propaganda found in films like Braveheart or TV series such as Outlander.  For example, the Battle of Culloden involved Scottish regiments fighting for the British side, and the Jacobite side had several regiments that suffered severely from desertion, plus a small English contingent; it was actually very little to do with England and Scotland, being rather more about religion and restoring the ousted House of Stuart.

But back to the borders …

The map above does not show Edinburgh, but it is on the northern edge of what is shown as Northumbria. The modern border is of course different; very roughly imagine a diagonal between the “Y” of Strathclyde, and a bit north of Bamburgh. The modern border was pretty much defined by the battle of Carham (or Coldstream) in 1018 when two Scottish kings (technically one was the king of Strathclyde) defeated an Earl of Northumbria. Later significant border changes worked out to be more or less temporary in nature.

This defeat (and loss of territory) was accepted by the kings of England partially because it has been alleged that the defacto border reflected the new border – England would have been quite weak in enforcing the “king’s peace” given it’s struggle to survive (essentially it didn’t being eventually conquered by the Normans which were essentially Danes or Norwegians with a French accent).

It is also the case that Northumbria would have seemed a remote part of the kingdom to both the Anglo-Saxon kings (most of whom were originally based in Wessex in the south), and to the Normans who were also distracted with “issues” in France. A case of not bothering when there were bigger issues at stake.

Which may very well have been a contributing factor to the North being somewhat grumpy and inclined towards rebellion; so much so that when Charles I raised his banner in the north to defeat parliament he was seen as a rebel.

So did those Northumbrians see themselves as Scottish after 1018? Almost certainly not, but they may very well not seen themselves as English or even Northumbrian either. The common people were far more likely to put more importance to their pre-medieval clan allegiances, and their medieval feudal lords. And those classified as clan chiefs or feudal lords would have pled allegiance to any overlord or king who was in a position to assist them.

To make things more complicated, the kings of Scotland often held the Earldom of Northumbria (thus were in theory required to swear allegiance to the English king) or Cumbria. Of course as an alternative to paying homage, the Scottish kings were just as happy to invade England – on at least one occasion reaching as far south as Dover.

And no medieval army behaved well on campaign – rape and pillage were considered standard forms of warfare at the time – so it is worth remembering that the English invasion in 1296 did not come in a vacuum. Yes the English behaved terribly in Scotland, but it was standard behaviour for armies at the time – soldiers expected to make money through plunder.

Trying to determine who invaded whom first is pointless not just because the conflict disappears into murkier periods of history, and because smaller scale “wars” (raids) probably occurred nearly constantly. The Scottish borders were a place of nearly constant raiding back and forth until at least the 17th century – there was even a special legal system in force in the borders (not that it helped much), and “real wars” were often raids on a larger scale.

So yes it is possible to argue that Edinburgh is English (and a great way to start an argument), but more importantly this all illustrates that nations are created and not natural. Someone from Berwick-Upon-Tweed could reasonably claim to be English, Scottish, Northumbrian, or even Bernician. If you look closely at history, you can actually see that nation-building happening with kings re-enforcing the notion of nation in order to protect their centralised power against magnates with ambition to replace them.

Just because nations are artificially created does not mean that they are meaningless, but it doesn’t do any harm to remember that they are artificial and that people on the “wrong” side of the border are different only in that some ruler from the distant past declared that they were different. Most national borders get fuzzier as you look closer at the people living near those borders.

May 232017
 

I woke up this morning to the news of the Manchester bombing this morning; learning about what was going on from a forum that had attracted some of the more rancid members of the far right. Who were busy blaming this atrocity on all muslims, but also on Syrian refugees; all this of course before anyone knew any facts because facts are irrelevant to the bigoted far right.

And a particularly nasty piece of work has labelled the victims “sluts” and “whores” (I’ve linked to a site that discusses his comments in order not to give him any extra ad revenue).

Now I am not in the habit of being sympathetic to any religious group – they all believe in imaginary friends. But they’re people and in many cases my fellow countrymen, so when a gang of pathetic little chickenshit cowards labels all muslims as terrorists, it is time to call them out on their bigoted bullshit.

Yes the evil scum who set off the bomb was a muslim; one born in Britain and not a Syrian refugee.

But :-

  1. It is almost certain that some of the 60 ambulances that attended were crewed by a muslim or two.
  2. It is almost certain that some of the police who were there helping people out were muslims.
  3. It is almost certain that some of those who opened their homes to accommodate stranded
  4. Some of the taxi drivers who turned off their meters and offered free lifts to those stranded were muslims.

Of course Mancunians of all faiths and none rallied around and helped out, but as muslims were being painted with the terrorism brush, it seems reasonable to highlight that many of those helping out were muslims.

May 202017
 

I just love messing around with run-time languages that I know relatively little about (and if your sarcasm detector isn’t flashing red about now, take it out and give it a good talking to).

The problem detailed here is something that you are unlikely to encounter unless you get into weird stuff like running an odd-ball window manager, aren’t content with the version of said window manager distributed with your Linux distribution, and are used to re-compiling things from scratch.

It all started when I upgraded Ubuntu on my work machine (to Zesty Zapus). The window manager version was upgraded from 3.5 to 4.0, which broke on my configuration file (3.5); not a big problem I thought, as I had already upgraded my window manager at home to 4.1 and reconfigured the configuration file. I copied the updated configuration file from home into place.

And it failed. Apparently I use 4.1-isms within the file. As I was not happy about tinkering with the file to downgrade it (in a language I know relatively little about), I decided to re-compile Awesome 4.1 instead.

Which failed with a weird error :-

» awesome --version
awesome v4.1 (Technologic)
 • Compiled against Lua 5.3.3 (running with Lua 5.3)
 • D-Bus support: ✔
 • execinfo support: ✔
 • xcb-randr version: 1.4
 • LGI version: [string "return require('lgi.version')"]:1: module 'lgi.version' not found:
	no field package.preload['lgi.version']
	no file '/usr/local/share/lua/5.3/lgi/version.lua'
	no file '/usr/local/share/lua/5.2/lgi/version.lua'
	no file '/usr/local/share/lua/5.3/lgi/version/init.lua'
	no file '/usr/local/share/lua/5.2/lgi/version/init.lua'
	no file '/usr/local/lib/lua/5.3/lgi/version.lua'
	no file '/usr/local/lib/lua/5.3/lgi/version/init.lua'
	no file '/usr/share/lua/5.3/lgi/version.lua'
	no file '/usr/share/lua/5.3/lgi/version/init.lua'
	no file './lgi/version.lua'
	no file './lgi/version/init.lua'
	no file '/usr/local/lib/lua/5.3/lgi/version.so'
	no file '/usr/lib/x86_64-linux-gnu/lua/5.3/lgi/version.so'
	no file '/usr/lib/lua/5.3/lgi/version.so'
	no file '/usr/local/lib/lua/5.3/loadall.so'
	no file './lgi/version.so'
	no file '/usr/local/lib/lua/5.3/lgi.so'
	no file '/usr/lib/x86_64-linux-gnu/lua/5.3/lgi.so'
	no file '/usr/lib/lua/5.3/lgi.so'
	no file '/usr/local/lib/lua/5.3/loadall.so'
	no file './lgi.so'

Which had me stumped for a while, and it turns out that DuckDuckGo didn’t have an obvious fix (one of the reasons for writing this).

Eventually I figured out that awesome was not finding the LGI module (I can be slow at times) which was odd because it was definitely installed. However it turns out that it was installed in /usr/share/lua/5.2/lgi. So despite having lua 5.3 installed, extra lua modules can only be seen if you have lua 5.2 installed?

The “fix” for this was to create an environment variable telling LUA to search for files in rather more places before starting Awesome :-

export LUA_PATH="/usr/local/share/lua/5.3/?.lua;/usr/local/share/lua/5.2/?.lua;/usr/local/share/lua/5.3/?/init.lua;/usr/local/share/lua/5.2/?/init.lua;/usr/local/lib/lua/5.3/?.lua;/usr/local/lib/lua/5.3/?/init.lua;/usr/share/lua/5.3/?.lua;/usr/share/lua/5.2/?.lua;/usr/share/lua/5.3/?/init.lua;/usr/share/lua/5.2/?/init.lua;./?.lua;./?/init.lua"

This was created by running lua from the command line and running print(package.path) to display the default setting, and adding the 5.2 equivalent for many elements.

As to whether it works or not, well I cannot be sure (I’m not going into work on a weekend just to check if the window manager fires up), but Awesome itself seems happy with the result :-

» awesome --version
awesome v4.1 (Technologic)
 • Compiled against Lua 5.3.3 (running with Lua 5.3)
 • D-Bus support: ✔
 • execinfo support: ✔
 • xcb-randr version: 1.4
 • LGI version: 0.9.1

So it can find LGI, but whether it can do anything useful with it remains to be seen!

May 172017
 

It may not be very funny, but the funny thing about WannaCrypt is that it is somewhat of a failure! Unless the authors are spectacularly stupid (not entirely impossible incidentally), they have no way to recover their ill-gotten gains. The pile of looted bitcoins they have acquired is fully visible, so any attempt to use those coins will almost certainly result in them being tracked down – they have attracted too much attention.

Which is another aspect of the WannCrypt malware – it has highlighted the vulnerability (MS17-010) and caused a huge vulnerability hunt. Which is causing those who wrote other malware (such as Adylkuzz) to gnash their teeth, because otherwise their malware would have quietly worked away in the background. The malware authors behind Adylkuzz have probably made more money than the WannaCrypt malware authors … and may well get away with their loot too.

Which is why other malware authors “wannacry” – the attention that WannaCrypt has gotten has ruined MS17-010 for them.

May 172017
 

It seems rather strange when you discover it, but Windows Update sometimes lies about what updates have been installed. I am not sure how often this happens, but it does happen from time to time. Which with WannaCrypt rampaging around is somewhat unfortunate.

What seems to happen is that Windows Update gets confused about what patches it has installed – it’s internal database gets corrupt. One possible fix for this is to remove the database :-

net stop wuauserv
cd %systemroot%
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv
rd /s/q SoftwareDistribution.old

When using Windows 10, you may well have to start (net start wuauserv) Windows Update services before stopping them. Once you have removed the directory, the next time you run Windows Update in the gooey, it will spend some time rebuilding it’s database and hopefully will then pick up the missing updates. No promises but this worked on at least one server that had unacknowledged missing patches.

Of course without a proper vulnerability scanner it may be tricky to determine when Windows is lying about being fully patched. The best bet is to assume it is lying whenever something like WannaCrypt comes along.

The other possibility is to look into something like Autopatcher which is intended for offline updates – you can download the Microsoft updates and use the tool to patch Windows computers from the downloads.