The bugs page on the DragonFlyBSD website has been updated with a security officer(s) address, on the off chance a security issue is found and a confidential contact is needed.
Simon ‘corecode’ Schubert has put together a Mercurial repo of the DragonFly source code, for those who like their SCMs decentralized.
I took my own advice and made a little experiment: a cheesy status page for Joerg Sonnenberger’s pkgsrc binary site. The page lists the update time, in descending order, for all the packages on the site. (and links to them too.) Could it be better? Yep.
Jeremy C. Reed is writing an article, and he’s taking a survey of DragonFly users.
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.
Joerg Sonneberger wants everyone to try out pkgsrc if possible; apparently large projects like KDE and Gnome are building, mostly.
UnixReview.com this week has two book reviews: Network Administrators Survival Guide and High Order Perl (I saw the book author, Mark Jason Dominus, at a conference a while back, come to think of it), an article about IPC called “Networking’s Easier than Programmers Realize“, and an article about forensic CDs, which is a cooler way to say “rescue CD”.
Let’s say you want to debug a crash, but it was caused by a separate kernel module? Hiten Pandya has a way to use asf(8) to get at the module-specific data.
Questions about multiprocessor machines and routing ability led to this post from Matthew Dillon, who described the bottlenecks (and how they will be eliminated).
Sergey Glushchenko asked a question about how the LWKT scheduler functions, and Matthew Dillon wrote up a rather detailed answer.
BSDCan 2006 is looking for proposals for (technical) papers, for presentation at their next event in May, 2006.
Matthew Dillon’s posted his first patch that can make network interrupts multiprocessor-safe. If you don’t want to run bleeding-edge code, it’s worth reading for the explanation.
‘walt’ wrote up a rather nice description about how debugging works, or at least how it can work.
UnixReview.com has several new articles: “Making a Dashboard Widget for Systems Administration Purposes” (for you Mac/BSD users), “Common Network Protocols“, focusing on Perl, and “John & Ed’s Scripting Screwups“.
Matthew Dillon posted his plans for the next release, which revolve around multiprocessor capability and the inclusion of pkgsrc. He also noted some of what he plans for immediately after the 1.4 release.
Joerg Sonneberger’s commit makes clear his latest RC system changes make DragonFly more compatible with pkgsrc.
Kamil Chatrnuch has created a DragonFly BSD group on Frappr, a “Friend Mapper” application. Add yourself and your interests, if you are so inclined.
The latest FreeBSD Status Report is up, with reports on a large variety of projects, including the results of a number of Google Summer of Code projects that used FreeBSD.
The pkgsrc guide (not DragonFly-specific; for that, see the wiki) has been translated into Brazilian Portuguese.
Why, yes, I am having a hard time finding newsworthy items today; why do you ask?