Volatility

I like being orderly. Those close to me may have already noticed this. I can handle chaos very well, but it's messy and --in my world-- demonstrates insufficient foresight and planning on someone's part.

Today, however, was pure chaos and was absolutely no one's fault. At least, no one I've been able to determine yet.

cuyahogarvr's kennel cough took a turn for the ugly overnight. Since his regular physician couldn't see him until Friday, we opted for a faster consultation via our local hospital's express screening office. (It's the branch of the emergency room area which deals with urgent but not life-threatening conditions.) After some time with oxygen and inhaled steroids, his colour returned and the hacking slowed considerably: the difference was night & day. The staff praised him for seeking treatment immediately rather than waiting it to get worse: he's probably cut his prescription treatment time in half.

Even before we left the house for this minor adventure, I had noticed that my VPN access to the office systems had locked me out. I could log into the web-based email server but only intermittently. This was severely annoying as I was planning to remotely upgrade the firmware on some IBM blades. Bugger

After filling cuyahogarvr's handful of prescriptions (and grabbing a couple of donuts for me), we stopped at home briefly then headed to the post office to send a priority letter and the local grocers for yogurt.

Back at home again, I found my VPN was no better. And the cabling project which was originally scheduled for Wednesday had been moved up to today. Figures.

The pain involved with this cabling project I can squarely blame on particular individuals who did not prepare in advance. For the love of god, if you want me to hook up a serial device to a console server, could you at least tell me the baud rate, parity, stop bits and flow control handling for the damn port?! And my account on the console server should have been created three months ago when I started! WTF?!

Anyway, the 30 minute project turned into four hours of hell but it is done. Unable to find the write firmware patch file on IBM's web site, I had to punt that little operation until tomorrow: I've now prepared a stand-alone boot CD-ROM which will do the job.

BTW, cuyahogarvr is sounding & looking vastly better tonight than this morning... the miracles of modern medicine!

To bed now and to continue reading up on pharoahs from Egypt's New Kingdom period. Tomorrow night, I work the night shift.

Volatility

I like being orderly. Those close to me may have already noticed this. I can handle chaos very well, but it's messy and --in my world-- demonstrates insufficient foresight and planning on someone's part.

Today, however, was pure chaos and was absolutely no one's fault. At least, no one I've been able to determine yet.

cuyahogarvr's kennel cough took a turn for the ugly overnight. Since his regular physician couldn't see him until Friday, we opted for a faster consultation via our local hospital's express screening office. (It's the branch of the emergency room area which deals with urgent but not life-threatening conditions.) After some time with oxygen and inhaled steroids, his colour returned and the hacking slowed considerably: the difference was night & day. The staff praised him for seeking treatment immediately rather than waiting it to get worse: he's probably cut his prescription treatment time in half.

Even before we left the house for this minor adventure, I had noticed that my VPN access to the office systems had locked me out. I could log into the web-based email server but only intermittently. This was severely annoying as I was planning to remotely upgrade the firmware on some IBM blades. Bugger

After filling cuyahogarvr's handful of prescriptions (and grabbing a couple of donuts for me), we stopped at home briefly then headed to the post office to send a priority letter and the local grocers for yogurt.

Back at home again, I found my VPN was no better. And the cabling project which was originally scheduled for Wednesday had been moved up to today. Figures.

The pain involved with this cabling project I can squarely blame on particular individuals who did not prepare in advance. For the love of god, if you want me to hook up a serial device to a console server, could you at least tell me the baud rate, parity, stop bits and flow control handling for the damn port?! And my account on the console server should have been created three months ago when I started! WTF?!

Anyway, the 30 minute project turned into four hours of hell but it is done. Unable to find the write firmware patch file on IBM's web site, I had to punt that little operation until tomorrow: I've now prepared a stand-alone boot CD-ROM which will do the job.

BTW, cuyahogarvr is sounding & looking vastly better tonight than this morning... the miracles of modern medicine!

To bed now and to continue reading up on pharoahs from Egypt's New Kingdom period. Tomorrow night, I work the night shift.