Networking didn't work after kernel upgrade: br0?

I did an 'apt-get dist-upgrade' and there was a kernel upgrade, so I rebooted. When the system came back there was no functional networking. Everything looked fine, I couldn't reach anything besides loopback.

On a hunch, I commented out br0 interface from /etc/network/interfaces and bounced networking (/etc/init.d/network restart) and all OK.

Then for grins I added br0 interface back and bounced networking again and, huh, all now seemed OK.

So I tried rebooted and all was still OK.

Chalking it up to a mystery for now unless problem returns.

Another dyndns false alarm - put weekly force into place

I got another ddclient false alarm, where my daily cron job seems to lag just a day behind dyndns sending me an email warning.

This time I decided to add a cron job that does a forced update once a week to get rid of this race condition. Start my copying over the daily cron job:

# cp /etc/cron.daily/ddclient /etc/cron.weekly/

And then editing it to include '-force':

# vi /etc/cron.weekly/ddclient

End result looks like this:

#!/bin/sh
/usr/sbin/ddclient -syslog -force

Upgraded to Virtualbox 3.0

I notiec that Virtualbox 3.0 was released, so I upgraded my previous install using the directions from www.virtualbox.org. This time I went the route of editing /etc/apt/sources.list by adding the following line:

deb http://download.virtualbox.org/virtualbox/debian jaunty non-free

Then adding the Sun VBox key:

wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | sudo apt-key add -

Then did the install:

apt-get install virtualbox-3.0

Then I also downloaded and installed the new 3.0 version of the SDK from the Virtualbox download page (which seems to have been updated to work with Python 2.6 btw).