It was only a matter of time until Microsoft came out with their own version of a watch. They likely saw Apple’s offering then stomped their feet and screamed, “But we want in on this, too!” View it here.
While bantering between ourselves over IRC, commenting on a conference call led by a higher-ranking mid-manager in the company:
Engineer 1: Did you grab yourself a Bullshit Bingo sheet before they started? http://www.bullshitbingo.net
Engineer 2: I should have.
Engineer 1: Feel free, of course, to mark off the similar phrases.
Engineer 2: After this call I’m going to the liquor store for lunch.
This was all on the heels of a conference call that I had to have with a customer (one of our Sr. Developers) to explain the complexities of adding a DNS entry. I suspect that they expected things to be complex, difficult, challenging, or otherwise bordering on impossibility because they have no exposure to such things.
I spent 25 minutes explaining to them that it’s a 20-second edit followed by a 5-second commit.
So, yes, I believe the soup of the day is, in fact, going to be whiskey.
Tractor pulling, just down the road a piece from Casa de Juan:
God, it’s a beautiful thing.
And there’s this gorgeous thing out in Pinckneyville, Illinois:
That’s just 110 HP on that Case steamer and it competes effortlessly against 600+HP gassers, diesels, and turbines.
Mass and gearing gets the work done.
The whistle helps, too.
Oh, and that shower of sparks also helps keep the
Priuses Prii away.
Somebody asked me a question in IRC and he was impressed that I responded with a terse, grammatically-correct, correctly-capitalized and punctuated, “No.”
Even in instant messages — even in text, MMS, and SMS messages — that is, indeed, precisely how I roll.
So far, no really serious problems with Yosemite. Apple changed some iPhoto/iCloud/Photostream behavior, which interrupted my workflow a bit until I figured out that I had to turn off Photostream on my iPhone then turn it back on to sync properly.
One issue I did have is with my RT-Systems control cable for my FT-817; it stopped working.
I checked /dev, and it was no longer there. Pull up System Information and it showed it was connected, so that’s good, but its absence from /dev meant that the OS was probably not even loading its driver.
So, off to /var/log/ for a quick check of system.log and confirmed that OS X was definitely refusing to load the RT-Systems’ “FTDI” USB driver:
# sudo grep -i ftdiusb system.log system.log:Oct 17 07:01:06 blah.esthermofet.com sudo: john : TTY=ttys000 ; PWD=/dev ; USER=root ; COMMAND=/sbin/kextload /System/Library/Extensions/FTDIUSBSerialDriver.kext system.log:Oct 17 07:01:08 blah.esthermofet.com com.apple.kextd: ERROR: invalid signature for com.FTDI.driver.FTDIUSBSerialDriver, will not load
Invalid signature? A few minutes’ checking of the magical Google and it appears there’s no option to whitelist any drivers in 10.10. But we can just disable the requirement to have any drivers signed by switching Kernel Extensions to Developer mode:
# sudo nvram boot-args="kext-dev-mode=1"
Type your password when prompted by sudo then reboot your Mac. Log back in, turn on your transceiver, open FLDigi, and get back on the air.