State of the binary build

Here’s the state of my build of pkgsrc-2010Q4 packages:

  1. DragonFly 2.8/i386 – in progress
  2. DragonFly 2.8/x86_64 – in progress
  3. DragonFly 2.9/i386 – just started (happens on Avalon)
  4. DragonFly 2.9/x86_64 – in progress

So it will be some days yet…  building over 4000 packages total is never quick.

Lazy Reading: cheatsheet, disks, pkgsrc, more

Normally I hold this for Sunday, but I’ve got a good batch of links already.  Something here for everyone, this week.

  • A git cheatsheet, and another git cheatsheet.  I may have linked to the latter one before, as it looks vaguely familiar.  Anyway, bookmark.  (Thanks, luxh on EFNet #dragonflybsd)
  • What should you do about bad blocks on a disk?  Get a new disk.
  • If you ever wanted to port software, there’s a pkgsrc developer’s guide (thanks Francois Tigeot) that shows you how.
  • It’s NOT LINUX, for the billionth time.  It’s BSD UNIX (certified, even) under there!
  • Children of the Cron“.  An entertaining pun.  (via)
  • Nothing to do with BSD, or even computers, really: Gary Gorton, interviewed about the recent financial crisis, at a Fed bank website (!?).  Interesting because I like economic matters, and because it’s the first web page where I’ve ever seen pop-up links added usefully, as a sort of footnote that you don’t have to scroll.  (via)
  • Michael Lucas recently had a machine broken into.  Since everything on the machine is suspect, he’s using Netflow data to figure out when it happened, and how, which is not surprising given his most recent book.  He has two posts describing how he backtracks his way to the probable source.
Ads off the page

I removed the Google ad off the sidebar; it was making me enough cash to buy a sandwich on a yearly basis.

I’ve replaced it with a link to my Amazon wishlist.  If you’re feeling generous, you can buy me a book!  If you aren’t, you can just keep reading, and I’ll keep posting.

Phoronix benchmarks for Hammer

A Phoronix test of DragonFly’s Hammer filesystem turned  up, via Siju George.  It’s not really a benchmark as much as it is a speed test, and it’s not a realistic comparison, but it’s interesting to see numbers.

They need a graph that shows how much historical data can be recovered by each file system, or how long fsck takes after a crash.

Update: Matthew Dillon points out the many ways these tests are wrong.