Of 1.4 and 1.5

Matthew Dillon has posted a description of what remains to be accomplished before the 1.4 release, and just when that will happen, and he also has a detailed plan of what he’s going to do in 1.5. (Which, when stable, will be DragonFly 1.6.)

That second post contains several special things to note:

  • 1.5 will be significantly unstable (at least compared to the previous development versions), so stick with 1.4 for a while if you don’t want trouble.
  • The introduction of a new acronym that I daresay we will hear more and more often: cache coherency management system (CCMS).
  • ZFS! (See Flash demo)

New Sys Admin CD out

Sys Admin Magazine has a new CD out that contains all issues of their magazine (1992 through 2005) and all the issues of The Perl Journal (1996-2002). I think I have all the paper issues of the Perl Journal around here someplace…

If you like Perl and miss the Journal, there’s also The Perl Review, which can show up in both print and PDF form. I like the paper, but I can back up the PDF…

Spare time testing

Want a project for your winter vacation? Matthew Dillon wrote in a post that I don’t have a link for:

I would still like to have a regression suite that can be run with a simple ‘make DESTDIR=(some_place_with_lots_of_space_available)‘. It would be a good project for someone.

Pileup: pkgsrc, cable hell, and crash autoreports

I have a number of small posts to link, and I’m placing them in one article: First, Joerg Sonnenberger mentions that he is updating his pkgsrc binary collection on an ad-hoc basis, though not everything is there yet. (Tracking updates is an afternoon project that would be enourmously beneficial, if anyone wants to try it…)

Also, Bob Bagwill contributed his own description of How Cabling Should Be. Last, Hiten Pandya commented on the idea of automatic crash reports, much like the “Feedback Agents” that upload crash information on the Windows platform.