Deciding to return to couples counseling with Microsoft

I’ve made no effort to hide my disdain for so many things Microsoft, that I doubt anyone I know could accuse me a being a fanboy with a straight face. My blog probably doesn’t represent some of the more cynical opinions I have, but I assure you my heart has been hardening for years. What did I learn today that was impressive enough to write about?

Today, like most days, I’m casually browsing posts at Hacker News when I run across this link.

Having been a Dropbox user for a long time, recently considering upgrading to a paid account for the additional storage, I now find that Microsoft just might — MIGHT — offer an alternative that’s worth using. Why not just give it a shot and see if Redmond has managed to learn what makes products like Facebook, Instagram, Firefox and countless other bleeding edge web solutions so appealing to consumers. (note: if you’re one of those people who always seemed to give Microsoft a fair chance to impress you after countless discouragement and crap products, you’re probably not the target audience of this post.) Continue reading Deciding to return to couples counseling with Microsoft

BIND 9 Error “has no address records (A or AAAA)”

The title of this post is important.

It’s important because the string in quotes above, “has no address records (A or AAAA)”, is the Google search that eventually lead me to solving a major annoyance and a likely broken BIND zone. The actual error I got was “zone INTERNET-NEXUS.COM/IN: NS 'NS.KELLEYFAMILY.COM.INTERNET-NEXUS.COM' has no address records (A or AAAA)“. Obviously this error is so isolated that Google wouldn’t return any results. Searching various versions of this error didn’t produce better results.

Finally, I stripped the error down to the key pieces (the quoted text in the post title) and found a solution to my problem. The solution to this problem, by the way, was bang-your-head-on-a-brick-wall stupid. Continue reading BIND 9 Error “has no address records (A or AAAA)”

Instagram Engineering

I’m a big fan of startups and generally lots of different technologies — particularly cool stuff I’ve never even heard of. One business that’s been kicking ass and taking names is Instagram. Their engineering prowess is impressive, if, for no other reason, they explain it in a fundamental, easy to understand way for those who have been around technology for a while and understand a lot of the core competencies. One could make the argument, though, that by telling the planet what your back-end looks like, you open yourself up to easy competition. Granted the details are missing and like anything else It’s not as easy as it looks, but just knowing what tools work well together is a HUGE migraine you won’t have to worry about. At any rate, Instagram engineering irregularly posted these design snippets to a Tumblr blog.

A few days ago, Instagram, after a mere 2 years in operation was acquired by Facebook for a paltry 2 billion US dollars. I don’t know if they’re headed toward corporate assimilation, or if, as Zuckerberg claimed, they will stay independent. I’m not taking any chances that the very cool write-ups they did will eventually be wiped from the Internet. What follows are all the entries (as of today) from http://instagram-engineering.tumblr.com/ for the simple fact that I hate digging for cool articles that have been removed.

Good luck guys. I hope it was a good decision.

Continue reading Instagram Engineering

Vmware: “SIOCSIFADDR: No such device after cloning”

Cloning a VMWare Ubuntu Linux image and renaming the host can force you to fix more than one thing. Here’s a handy set of tips / articles I found related to this.

http://www.ubuntugeek.com/ubuntu-networking-configuration-using-command-line.html
http://ubuntuguide.net/fix-ubuntu-sudo-errorunable-to-resolve-host
http://muffinresearch.co.uk/archives/2008/07/13/vmware-siocsifaddr-no-such-device-eth0-after-cloning/

Update: April, 22 2012

In addition, if you clone an Ubuntu image that runs on your local Windows 7 workstation — and you are using VMWare Workstation — you may see the network adapter disappear when you do an ifconfig. I found the explanation and fix from the link below quite helpful.

http://www.orzeszek.org/blog/2010/07/25/fix-missing-eth0-when-cloning-ubuntu-vmware-virtual-machines/

Basically, you need to delete the old configuration file.
sudo rm /etc/udev/rules.d/70-persistent-net.rules