Halfwittering.
And now, a short section from here:
The official SAAB service schedule states that at every service the key fob batteries must be checked or changed as required. When cars fall out of the dealer network as they get older, this simple procedure tends to get overlooked. Usually -when 9-3 or 9-5 owners least expect or need it- a message appears on the SID "Change key fob battery".
Owners of NG900s or 9000s with the optional SAAB alarm/immobiliser were less fortunate: if the fob didn't unlock the doors, it was time to change the batteries!
... Which is entirely and tiresomely correct. I have some spare CR2016 cells now, however at mumble-PM on a busy-for-the-AA Saturday night, I wasn't quite so much of an adult...
So yesterday was a bit surplus because of $reasons and today not much better. I really do have the brains of someone dim and gormless, while the relevant dim & gormless person is probably joyriding my brain about town, bashing into cardboard boxes stored in alleyways and generally ignoring the rev-limiter on my superego. The bastard.
For instance:
We have a pile of Puppet manifests that describe some moderately complex multi-VM systems. Because Puppet's a bit poor on cross-machine config, a lot of the complicated bits are tied down to IP address and/or hostname.
Were one wanting to bring up a number of these systems in an isolated environment for the purposes of testing, one would likely have to go through the faff of generating a set of hostnames, bagging some IP space, C&Ping the relevant bits of config over to the new set of addresses.. And only then could you bring up some new VMs for the purposes of doing some work. It's amazingly much more better than it used to be, but it's still a complete faff and really not repeatable. Unless you're going to do something like carve out wedges of pre-allocated IP space and label each bit as not to be fiddled with, by order, The Mgt.
A much more scalable, sensible and automatable approach would be to use some kind of config DB that the machines would connect to on start up so that they could announce their presence and function, should other kit be interested. The mildly complex part of that approach would be getting the ordering right or building it all such that the component parts have the brains to poll the DB on and off 'til they get a sensible answer. If you make that work, then your rig no longer cares about hostnames or IP addresses, which is just a Good Thing in this modern world of toys-on-demand.
... And I'm totally failing to get to grips with any of this.
On the other hand, I have Hunter/Land-Rover green nail varnish.
I also have a clean keyboard for the first time in a while. Were this five or seven years ago when people who read LJ also had the patience to deal with the largely missing photo-handling capability, I'd be asking for pictures of yr keyboards. However, passive-aggressive paragraphs (or entire posts) about 'no-one being on LJ' aren't any fun and I suspect El Reg has the premier collection of jallop-and-breakfast-encrusted keyboards.
I would like to point out that my keyboard was not encrusted with breakfast or jallop.