Are you running DragonFly on a laptop system? Please mention the brand and model number on the appropriate page on the DragonFly website. (Also: Laptop tips and tricks, thanks to Alexander Polakov)
The main page of the dragonflybsd.org site now has a feed of the most recent 10 articles from this Digest.
I don’t know how recently this recording was made, but Dru Lavigne found a recording of Jeffrey Hsu (longtime DragonFly committer) taking about How To Get Started with Kernel Programming.
The 2.4 release looks to be about a week and a half away; if you’re a committer, please plan to make drastic changes after the release, if possible,
It’s alliterative, so it must be good. Brian Gianforcaro has offered to set up Doxygen for DragonFly, which if nothing else would show where more comments were needed.
The 2.4 release will be later this month; Matthew Dillon has details. He appears to have already fixed the Hammer bug he mentions as a final issue before release.
Oh, look – Alex Hornung made Linux emulation work again. Thanks!
There’s some new HP server hardware out there, and Hasso Tepper found some problems (and lists some potential solutions) with installing DragonFly, mostly centered around keyboard handling. It sounds like NetBSD’s keyboard mux may solve it for us, if someone’s willing to add it…
Alex Hornung has posted a summary of what Unix98 pty devices are, and how they are supported under DevFS. If something screwy happens, there’s even a debug option to turn on.
Say hello to the newest DragonFly committer: Alexander Polakov. Hello, Alex!
If you want to use kerberos for logins, you need pam_krb5.so. However, that’s not built automatically since kerberos was removed from the base system in DragonFly. The solution is to install security/heimdal from pkgsrc and follow corecode’s brief instructions.
Want to make Hasso Tepper’s day? He’s posted 4 separate bugs for DragonFly that revolve around pkgsrc packages: sysutils/hal, sysutils/libgtop, audio/pulseaudio, and HTML5 video in FireFox. All of these (except the last) are issues that have been present for a while, and fixing any of them will help a number of other pkgsrc packages work correctly on DragonFly. If the work appeals to you, please dig in.
Qemu, used for testing 64-bit DragonFly, has been updated to version 10.6 in pkgsrc. BSD user emulation compiles, but doesn’t run, as Hasso Tepper has found out. He’d appreciate it if someone could investigate… (his hands are full with the rest of pkgsrc.)
Hasso Tepper has written up a mini-FAQ for pkgsrc and DragonFly. Among other points, he asks that people try to politely submit DragonFly-specific changes upstream, past pkgsrc, to the software creators themselves. This creates the least amount of work for pkgsrc developers and DragonFly users.
The libtiff package has been found to write out incorrect TIFF files in version 3.9.0. If that’s what is installed on your system, please update now.
DMA, the DragonFly Mail Agent, has been updated so that it can deliver email from cron job output. DMA is a former Summer of Code project to make a local-only mailer for DragonFly systems, so that larger mail transfer agents (like Sendmail or Postfix) are not needed on a system that isn’t designed to receive mail from external sources. There’s a TODO list (click the gitweb link) if you’d like to contribute.
Siju George asked about updating pkgsrc packages, both on DragonFly mailing lists and on pkgsrc-users@. The ensuing discussion can be boiled down to several alternatives: pkg_chk in a separate chroot, pkg_rolling-replace, or pkgin, pointed at avalon.dragonflybsd.org. I’ve used pkg_rolling-replace several times with good results, and it may be possible to convince it to use binary packages, too.
This article about how to not treat project contributors reminds me: have you contributed to DragonFly? (and I don’t mean as a committer) Make sure your name is on the Team page.
The 2.4 release will attach disk drives by serial number. Matthew Dillon’s written up a quick HOWTO that describes how to use it. The interesting effect, as he notes, is that a drive can be attached in almost any way – a firewire enclosure, directly to the motherboard, through a card, etc. – and the machine will still happily boot without any changes needed.
For those of you running DragonFly 2.3.1 or later, I’ve updated the pkgsrc-2009Q2 packages on avalon.dragonflybsd.org to the latest versions on that branch. If you’re curious to see which were updated, I have a list after the cut: