The FAIL bot.

There are times when you just have to do things the hard way. For example, on finding a bug in a piece of software deployed to thirty-odd client systems, it would generally be considered a good idea to connect to those systems, ascertain whether or not said system was affected, and then patch and test as required.

That would be a good way to do it.

The FAIL bot would not be a good way to do it.

What the FAIL bot does is connect to all client machines, have a cursory glance around, and then blatt a big wad of binary FAIL onto the system, whether it needs updating or not.

I wonder which approach we’ll go for….

Related posts

Make that two years

The Web is dead, consumed by adverts that chase you around the page, cat...

Oh my.

So, it looks like I'm averaging a post a year at the moment. That's...

State of the cluster

Here we see, in all its glory, the little mini-cluster of Computery Goodness which...

Abe Yospe’s Wife.

There is a scurrilous rumour circulating that Abe Yospe's wife googles things really quickly...

Latest posts

Horse Whisperer (1998)

M'okay, overbearing workaholic mum takes extremely traumatised daughter and her equally traumatised horse to...

Make that two years

The Web is dead, consumed by adverts that chase you around the page, cat...

Oh my.

So, it looks like I'm averaging a post a year at the moment. That's...

State of the cluster

Here we see, in all its glory, the little mini-cluster of Computery Goodness which...

Creating a Bramble

So, my current Raspberry Pi cluster isn't really a true cluster - it's really...

Leave a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.