Matthew Dillon, as part of a larger discussion, chimed in with some sensible descriptions of licensing and how it applies to the recent OpenBSD/Linux kerfuffle.
Hasso Tepper added a whole pile of uftdi(4) drivers. Why? Apparently it’s cheaper to buy from FTDI than it is to buy a vendor ID from usb.org.
Noah Yan posted how to apply his recent patch for building an AMD64 kernel. Be warned; it does not create a full usable system – yet.
There’s an effort to make the ‘official’ pkgsrc logo happen; previous discussion was described here. It looks like the simple version is the candidate; there’s a fun, alternate version that unfortunately won’t reproduce well.
pcc has been added to NetBSD (via pkgsrc) and OpenBSD, and Steve Mynott has been messing with it on DragonFly. It doesn’t work as a replacement for GCC, but it looks promising. There are other alternatives in progress, too.
This week, BSDTalk talks about sysjail, the Open/NetBSD version of FreeBSD ‘jail’, with Michael Dexter. (Yes, I realize that’s an oversimplification.)
Sepherosa Ziehau has a patch that makes it possible to assign polling(4) to specific CPUs.
Update: There’s a new version of that patch.
If enabling ACPI means that some of the devices attached to your computer can’t be found, YONETANI Tomokazu has a patch that may fix it.
Sascha Wildner has added two new man pages: kernconf(5), for explaining kernel options, and firmware(9), for the process of loading firmware images into the kernel.
Chris Turner is also a new DragonFly developer with commit access. Welcome, Chris.
Hasso Tepper has a patch that appears to fix net-snmp; it can be downloaded for someone who needs SNMP now, and it should hopefully be integrated into pkgsrc soon.
DragonFly’s newest developer with commit access: Noah Yan, already known to be working on the AMD64 version of DragonFly. Welcome, Noah.
Hasso Tepper has brought in extensive changes to agp(4), from FreeBSD. For a full list of the many new supported devices, puzzle through the man page diff.
There’s a good number of commits to DragonFly that I don’t mention on the Digest because they are relatively small, or not necessarily part of a larger plan. However, I’ll take a minute to mention the work by Sascha Wildner; he has kept the man pages in DragonFly up-to-date almost single-handedly, and done an excellent job. How good? See this excerpt from the IRC channel #dragonflybsd on EFNet:
(17:17:57) corecode: wow linux man pages are unreadable
(17:18:00) corecode: incomprehensive
(18:11:52) _hasso_: corecode: linux doesn’t have swildner ;P
YONETANI Tomokazu reports that DragonFly will boot on his Core 2 Duo MacBook Pro, though Daniel Tralamazza reports it won’t boot on his 1st generation MacBook Pro. I didn’t know this was possible…
Update: Darn.
Sepherosa Ziehau has made changes to the nfe(4) driver that, among other things, allow a card with that chipset to transmit data at full line rate.
If you haven’t already, you should make sure your NFS mounts can be put into the background. Sooner or later, it’ll save you a lot of waiting.
Sepherosa Ziehau has added ‘in-progress’ support for a number of Broadcom networking chipsets. Check the commit message for features, credits, and so on. Thanks, Sephe!
Dave Hayes posted his scheme for upgrading OpenSSL on a DragonFly 1.8 system to the latest version. This is useful if you haven’t yet moved to 1.10.1, and want to avoid recent OpenSSL security issues.