Archive for January, 2007

January 28, 2007: 4:50 pm: MatthewFirefox, Technical

look at dojo.com for the info… I especially like the change-the-icon tweak

January 27, 2007: 12:49 pm: MatthewApplications, Technical

Carbonite - looks interesting but isn’t currently Mac or Linux compatible. Hmmm… still, might be good for protecting less-technical folks’ computers.

January 24, 2007: 7:33 am: MatthewDebian, Linux Misc, Technical

So I had a hardware (onboard NIC) failure and had to change my network configuration. The darn OS (Debian Sarge) wouldn’t actually disable the onboard NIC so I had to give it a goofy address in order to make it work… but what I neglected to think about was how packets were going to get off the box. Since the ETH0 interface had a default gateway, I left it there… which was my mistake. I should have removed the gateway since the server thought it was multihomed, but instead I ended up finding the problem by dumping the ROUTE table and then removing the second default route. It only took me a bit more than an hour for a fix that should have been about 10 minutes.

Lessons: (1) I hate onboard equipment and (2) never forget your routing!

: 7:32 am: MatthewTechnical, Tips and Tricks

How to investigate and kill off all those nasty autostart processes in Windows?

start:run:msconfig

January 14, 2007: 3:02 pm: MatthewTechnical, Tips and Tricks

Good average power supply calculator

January 6, 2007: 6:40 pm: MatthewDebian, Technical

So I was trying to install a new package and it very cleverly decided somewhere in the Debian dependencies that I didn’t need a kernel. Thankfully, APT noticed and screamed loudly so that I would stop the insanity! However, a few packages had already been ripped out of the system and I had to do emergency repairs. ‘apt -f install’ does wonders.

However, it pulled out php4 and php4-mysql, as well as wordpress and gallery2. When I reinstalled and tried going to my sites, they all were screaming at me. For example, Wordpress 2 said:

Your PHP installation appears to be missing the MySQL which is required for WordPress.

but I knew it was blasted well installed. After pounding on the system to ensure it was there, restarting every service that could have been affected, logging into mysql, checking the config files, and searching the web, I remembered having a problem when I installed php4-mysql… so I used a little magic trick that (thank goodness!) worked.
dpkg-reconfigure php4-mysql
All I had to do was tell it to activate the php-mysql connection, and we were back. Jiminy, what a scare, though!