El Capitan 10.11.5 upgrade

… or as I like to call it, El Kabong because it’s so comical. Whenever Apple releases an upgrade, I don’t expect much. They seem to fix almost nothing, but new bugs seem to creep in.

So, what’s the score this time just minutes after rebooting?

As for any upgrade, OS X automatically logs me in to the last account from which I started the upgrade, which is a huge security violation. There is no circumstance I can think of where auto-logging in is the best choice. You basically can’t walk away from an upgrade if you’re in a place where you can’t trust the people around you.

Three volumes failed to mount. Replugging them doesn’t help. I’m always forced to reboot again. And so I did.

Every single time I reboot, OS X doesn’t like something about one of my drives. It won’t say which one, but it always complains about an unreadable drive. I click Ignore, and it mounts anyway. So the dialog is always wrong.

There is one high-impact bug in particular that I’ve been complaining about and that’s the runaway process bug that occurs frequently, hammers my disk by writing and renaming a file hundreds, if not thousands, of times a second, and can run forever until I reboot once, twice, or just give up. I sure as hell hope this update fixes that but I would bet it won’t.

CrashPlan is like a teenager

in that it doesn’t do what you tell it to do.

It’s supposed to be backing up to two sets; the first one in the image is to the cloud and is a subset of the second one. So why does CrashPlan say it’s only going to backup 1 GB instead of the 150 GB it’s been told to backup?

CrashPlan Fuckup

This is after I forced it to rescan when it told me it was only going to backup a 1000 files. When I left it, it was scanning well past that number, yet it didn’t back them up. So, for the umpteenth time this year I have to babysit CrashPlan to figure out why it’s being so petulant.

Continue reading “CrashPlan is like a teenager”