VirtualBox vdi disk image failed

I’ve had physical drives fail before, but this is a first. I’ve used VirtualBox on and off for years for those times when you need to fire up a guest os and it’s always worked fine, no issues. I just installed Fedora 16 on a new virtual drive image and on the first reboot after installing the VM crashed. After that point VirtualBox wouldn’t boot it any more saying the vdi headers were corrupt.

Wow, ok. Other than messing with headers physically in the image file, it appears there’s no repair options or tools. This is the first time I’ve seen this, so giving it the benefit of the doubt, I downloaded the latest version, 4.1.8, created a new vm and new disk image, and I’m installing again.

Configuring mysqld to listen for remote connections

I’m not sure if I originally configured this or if this is the default. My my.cnf file had this line in it which configures mysql to only listening for incoming connections from localhost and ignores all remote connections:

bind-address            = 127.0.0.1

Changing this to be the real ip of the server will allow it to listen for remote connections.

Apple sue-fest continues: HTC

Come on Apple, give it a rest. Get back and get busy with what you do best, innovation, and not turn into the next Microsoft and make your money from legal action against your competition (e.g. the Microsoft (SCO) vs Linux distro companies fiasco that went on for years and really went no-where for Microsoft)

As I said last week, you’re in danger of becoming the next Microsoft in more ways that one – your closed approach to iOS is blatant vendor lock-in, and you’re gunning down your competition in needless legal battles. If you carry on with this sue-fest, you’re putting me off from buying any more of your products. I love Mac OS X and my MacBook Pro, but I can’t bring myself to buy my next one from a company that pursues these kinds of legal action against your competitors. My next laptop will be running Linux (again) at this rate.