Upgraded to NetBSD 5, 2009-05-02 00:00:00 #
I just upgraded my soekris from NetBSD 3.1 to NetBSD 5.0. I actually did a fresh install following my own docs at and am still working on getting all of my packages installed now. So far the systems seems fine, although I'm having a little more trouble fitting it onto 512MB. :) Speaking of packages, I'm still waiting on the install of apache to finish (pkg_add seems stuck in select() or something) and I wanted to get this site back up, so I just fired up /usr/libexec/httpd (bozohttpd), which is now included in NetBSD, so I didn't have to wait for pkg_add at all. NetBSD fester 5.0 NetBSD 5.0 (GENERIC) #0: Sun Apr 26 18:50:08 UTC 2009
binary patching for NetBSD, 2009-04-27 00:00:00 #
describing the beginnings of a tool which is like what was supposed to be. I personally look forward to single-command upgrades to my netbsd systems. :)
NetBSD should cannibalize wasabi systems, 2009-04-18 00:00:00 #
As noted in another blog, wasabi systems has gone away. It would seem that they donated WAPBL to NetBSD in a final act of charity before being forced to close their doors. Now that they're gone, I wonder if they have any other technologies they would be able to give to NetBSD or even sell to the netbsd foundation. Old hardware is probably too easy to sell for bill-paying, or else that would probably be nice too. Regardless, it's sad to see them go. Who will be the next big NetBSD-based company (other than microsoft via the sidekick, I mean) to give things a spin? On that note, microsoft donating work would also be nice. ;) Edited for typos..
pkgsrc dashboard - functionally complete, 2009-04-12 00:00:00 #
pkgsrc-dashboard is now, basically, functionally complete for its initial goals: If will take input from a single shell script on any pkgsrc client and create a website of reports telling you if the package is vulnerable, old according to a source repository, and/or old according to a binary repository. There are tons of possibilities when you get into this sort of thing, but I think that base functionality is pretty good. The server requires one daily sync of the INDEX from your local source repository, perl, DBI, and DBD::SQLite, and occasional find -exec rm to cleanup old reports. The client only needs to run a shell script every once in a while (daily is the highest supported frequency). pkgsrc-dashboard
DBD::DBM only supports tables with TWO columns, 2009-04-09 00:00:00 #
The subject says it all, and it's in the perldocs, but I guess I was lazy. I thought I could get away with just having little db files around, and I know that I could just use a packed value, or a bitmap, or whatever, but then I may as well just use a bdb directly! ugh, I guess I'll look at sqlite.