06 March, 2006
No New Packages Yet - Here's Why!
I really meant to have new packages out by now. It hasn't happened yet. Here is why:
- I electrocuted my firewall. Embarrassing, I know, but I did: I've got a little box based on a VIA Epia-PD6000E motherboard. Small, unobtrusive, black and acting as a file and print server and as a firewall (via separate UML). A few weeks ago, it got struck by lightning (well not really, just a surge, I suppose, during a thunderstorm), which took out the ethernet ports both in my cable modem and on the board. Last Thursday, I decided to put in a second fan serialised with the first one to reduce noise but keep airflow up. While I was putting it in, I fumbled around with a life 12V wire and touched one of the connectors of the single PCI slot - there was the tiniest of sparks and me going f@#$%%&ck. After that, the board was history... My dealer tells me I can pick up a new one tomorrow.
- I am getting the most spectacular crashes when using (as I have now narrowed down to) linux-image-2.6.15-1-amd64-generic (on amd64). Pretty much towards the end of a restore run, something segfaults and causes the init script to get respawned indefinitely - impressive but annoying. I have decided, though, that this is not related to my packages. Unfortunately, one can't yet report bugs against amd64 packages as the architecture is not yet integrated into the Debian infrastructure. Oh well.