Antonio Huete Jimenez wants to find anyone working on tmpfs for DragonFly; his post about it summarizes the work so far. He’s interested in working on it, in any case.
Why, BSDTalk 184 is our very own Matthew Dillon talking about all the recent changes in DragonFly, for a good half-hour! I’ve listened to about half of it so far… I hadn’t realized the significance of some of the changes in the last two releases. It’s also strange to hear someone mentioning the work you’ve done (pkgsrc bulk builds)…
Jan Lentfer’s posted the steps to test OpenSSL encryption – I link to them because it’s interesting to see the steps spelled out.
Jan’s also posted a patch to enable DNSSEC support throughout BIND and related tools. Test if this interests you. (and it should.)
There’s a recent libc vulnerability that appears to be present in every BSD and Linux flavor. (Nearly every? There’s a lot…) Antonio Huete Jimenez committed the fix, with instructions on how to just rebuild libc for thatupdate.
I’ve always said you can’t be too rich, too thin, or have too much RAM. (I’m paraphrasing a quote from the Dutchess of Windsor.) However, maybe you can have too much RAM. Recent changes by Matthew Dillon have made it possible to run the kernel_map out of RAM depending on the quantity of video RAM and system RAM in use.
This isn’t a significant danger; I’m highlighting it because it’s an odd problem. It’s easy to work around for now. There’s a new utility, kmapinfo, to show mow much kernel memory is being used.
Thomas Nikolajsen experienced firsthand a bug where downgrading a Hammer PFS master to a slave and then later making it a master again lost all data. Lucky him… The problem’s now fixed.
Jan Lentfer needs someone with cryptographic hardware that isn’t padlock (e.g. not VIA) to test his recent OpenSSL upgrade. Do you have hardware that matches? Please help.
Jan Lentfer noticed a lot of errors with his vr(4) card under load. Matthew Dillon suggested some reasons/fixes, and then made a commit that may fix it. Please test if you have an older Rhine card.
In response to a question about fine-grained vs. coarse locking, Matthew Dillon detailed the locking types used by DragonFly and the remaining work left to make the system able to function completely without the Giant Lock. (hint: VM, something Matt’s known for.)
There were some errors with the dragonflybsd.org domain, which are now fixed. This includes some issues in NNTP access to the discussion groups, which is why I don’t have a link for this.
This has been bouncing around other news outlets, but I’ll mention it here: There’s an out of data SpamAssassin rule that can potentially mark mail as spam because of the 2010 date. A mail to tech-pkg@netbsd.org describes the various fixes.
The step of ‘sa-update && /etc/rc.d/spamd restart’ seems to have fixed it for me. Incidentally, if you are using SpamAssassin, sa-update is a good tool to run on a regular basis.
As previously noted, some of Matthew Dillon’s work was potentially destabilizing. The “danger period” (I saw no issues reported) is over.
It’s New Year’s Eve Eve, and so here are a bunch of links I’ve built up over the past few days.
- Hubert Feyrer posted notes on how to mount fixed disks in KDE. This probably works on NetBSD, but I bet it would work on DragonFly too…
- pcc is now able to build an OpenBSD i386 kernel. Will it work for other BSDs? I hope so, eventually.
- The FreeBSD Foundation is in the last hours of donation for 2009 – give if you get a chance. Did you know they get Bad Code Offsets, like carbon offsets? I did not know such a thing exists, though it makes sense.
- Brian Kernighan talking about Elements of Programming Style, in video. (via) Kernighan’s book, “The Practice of Programming“, with Rob Pike, is an excellent read.
Newer disks are moving to 4KB sectors (more info), instead of the 512-byte sectors that have been in use for… decades? There’s been some recent discussion on how to support this, for booting DragonFly. It should otherwise work.
Matthias Schmidt is posting to Twitter about his time at 26c3 with other DragonFly developers, on his own feed and in @dragonflybsd. (if you are reading this via a Twitter link, you may already know that.) Follow the #26c3 tag if you want to see all the news about the event. A quick scan shows some interesting mobile phone security problems have been discovered. There’s streaming video too.
Matthew Dillon is working on moving more of DragonFly out from under the Giant Lock. This may mean some instability this week if you’re following the bleeding-edge. He’s already posted a warning and an explanation (with numbers!) of work already completed.
BSDTalk was recently linked here interviewing Randal Schwartz. Randal Schwartz and Leo Laporte, who create a podcast called “FLOSS 101 Weekly”, now have an interview with Scott Ullrich and Chris Buechler about pfSense. (via) It’s a nice bit of symmetry, and Scott was an early contributor to DragonFly – specifically, the installer.
I (that’s Justin Sherrill, for those reading this other places than the Digest) finished a build of pkgsrc-current on DragonFly 2.4.1 – these packages are available, though soon to be outdated by the pkgsrc-2009Q4 release, due 2010/01/01. This build was mostly to check compatibility before the release.
Everything that _why the lucky stiff did. (via) _why is one of those things that only the Internet lets exist. And he used DragonFly!
Roguelike games, evaluated via the Berlin Interpretation, on @Play. Also, a dedicated Roguelike handheld?
Naoya Sugioka is working on bringing tmpfs to DragonFly – I am a big fan of that idea.
top now uses CTIME, not WCPU.