The obvious joke should be “how can you tell?” Anyway, the csprng in DragonFly has been updated and IBAA is being used more often, and there’s more updates on the way.
Matthew Dillon posted a note about the next point release of DragonFly, coming within a few days. Chunks of it like the recent OpenSSL and Sendmail fixes are already on the 3.8 branch.
I assume I’ll be the one rolling it, and I plan to put together a 3.6.3 tag too, just so there’s a final version of 3.6 that has all changes rolled up.
If you’re building ports, it will treat OpenSSL as a dependency and bring in whatever version is available. If perhaps you want to use the version of OpenSSL installed as part of your base system, Robin Hahling has the answer for how. (This probably works on FreeBSD too.)
Sascha Wildner has removed some drivers in the x86_64 config. This will only really affect you if you use a custom kernel and still have entries for those drivers in the config file.
If you are saying “Hey, what about LibreSSL? And do I write it LibReSSL?”, it’s not set up as a portable release yet. Also, I don’t know the correct capitalization, either. There is some debate about the lack of notification from OpenSSL to LibreSSL, though other vendors were notified days before.
Binary dports packages for 3.8 have been built; they are available for download. (link goes to release versions of the packages. Future updates will be in ../LATEST)
For upgrades from 3.6: You can pull the 3.8 source normally with git:
git fetch origin
git branch DragonFly_RELEASE_3_8 origin/DragonFly_RELEASE_3_8
git checkout DragonFly_RELEASE_3_8
Assuming you are using an unmodified kernel, here’s the steps I usually do for an upgrade:
# make buildworld && make buildkernel && make installkernel && make installworld && make upgrade
After upgrading from 3.6, pkg (as designed) will download the appropriate 3.8 packages with
If you have DragonFly on a laptop, and a docking station for that laptop, it may be better supported now. (no, I don’t know exactly what acpi_dock does.)
Thanks to John Marino and people I don’t know the name of in the gcc project, DragonFly is now part of the gcc test suite.
“What about clang?” you say? We’re not picky; DragonFly works with either.
The slides from Francois Tigeot’s talk about benchmarking DragonFly with PostgreSQL are now online – link is to a PDF.
The May BSD Magazine is out, and Siju George has written an article about using Hammer on DragonFly. It’s a free download to read.
Imre Vadasz is our newest DragonFly committer. Welcome, Imre!
Matthew Dillon brought in Adrian Chadd’s sleep state changes for the ath(4) driver from FreeBSD to DragonFly; you may see reduced power usage if you have the appropriate hardware.
I’ve seen Atlassian Confluence, a Java-based wiki program, in a few places. Atlassian apparently offers their software at a discount (free?) to qualified open source projects. I set up Confluence 5.4 on DragonFly as a test run, and it generally worked. That’s great! I tried to set up version 5.5, and it will not start.
May 08, 2014 7:24:41 PM org.apache.catalina.core.ContainerBase startInternal SEVERE: A child container failed during start java.util.concurrent.ExecutionException: java.lang.InternalError: platform not recognized at java.util.concurrent.FutureTask.report(FutureTask.java:122)
This is annoying. DragonFly (or any BSD) is not supported by Atlassian for Confluence, so it’s not a surprise… but I was so close! Their product has a very nice interface and I was planning to replace Mediawiki at my workplace with it, for some internal documentation. This FreeBSD bug report is the closest fix I can find, but it’s old enough it shouldn’t matter now.
The reaction I have heard a number of times from new DragonFly users: hey, this runs really fast, even when I try to load it down!
The pkg tool, used in DragonFly (and FreeBSD) for ports, is at version 1.2. Version 1.3 will apparently be able to solve the problem where one port is ended and replaced with another. This is a problem that’s been around forever, and I don’t just mean with pkg. I don’t know how soon 1.3 will be out, or what version FreeBSD is at.
Just so nobody’s surprised: DragonFly process IDs now go an order of magnitude higher.
If you’re using DragonFly in qemu, virtualbox, whatever – but not VMWare – there’s a new virtio-net driver to try out.
The March issue of BSD Magazine is out, and this month has an article written by Siju George about how his company is using DragonFly and Hammer for backups.
Remember: If you have a particular port that’s not building in DragonFly, there may be a patch in pkgsrc that could be brought over, as John Marino points out.
DragonFly now has a ‘rescue’ system added in, which also functions as a way to mount encrypted filesystems. Does PAM work yet? I don’t know; I may be linking to this earlier than I need to.
All the dragonflybsd.org sites (www, bugs, gitweb, lists, leaf) should be available via https now, thanks to a wildcard certificate from InterNetX. Also, all the machines have an up-to-date version (1.0.1g) of OpenSSL installed to prevent the Heartbleed issue.
I’ve wanted more support for virtualized DragonFly systems. Sascha Wildner put together an experimental balloon memory driver to test out, and I ran it on two virtual machines separately, one with it loaded and one without, on the same host system. The problem is, I can’t tell what it does. The two machine reported almost the exact same RAM usage during a buildworld.
Any VMWare/virtualization experts out there able to tell me what needs to be tested to verify this?
In a thread about video cards on DragonFly, Francois Tigeot listed good ATI cards to try, and pointed out the VESA driver is probably your best bet right now with NVidia cards.
The acpi_thinkpad module (section? code?) has been updated. Update if you are on DragonFly 3.7, or be patient if you are on 3.6.
I wrote up some thoughts for the next release of DragonFly. There’s some project work in there for anyone interested. The next release should be near the end of May.
BSDTalk 239 is 55 minutes of talk with Baptiste Daroussin at vBSDCon 2013 about ‘pkgng’ on FreeBSD. The BSDTalk post doesn’t mention it, but it is the same pkg tool that DragonFly uses, so Baptiste’s plans are relevant to DragonFly too. (I haven’t had a chance to listen to the podcast yet so I don’t know how much he talks about DragonFly, specifically.)
Timezones are a human invention to describe the natural world, so they are changed according to human whims. That’s a grand way to note this change in timezones that is global but I noted in a DragonFly commit of tzdata2014b – look at the last entry.
One of the requirements to get NSS/LDAP working on (most) any unixlike system is to have dynamic binaries; meaning they are dependent on various libraries to run. Since you’re talking about programs for login when you’re talking about NSS/LDAP, that means if the libraries aren’t available, you can’t log in. DragonFly has static binaries just to avoid that problem.
Francois Tigeot proposed switching to dynamic binaries and building a /rescue directory with static backups, as is the case with I think FreeBSD and NetBSD. If you follow the thread, it looks like the best path is to use initrd instead. Initrd stands for INITial Ram Disk, and is the first volume the computer sets up to boot from BIOS. Since initrd gives the computer enough space to load all the needed modules (like Hammer2…), it works without making the computer dependent on various libraries or having a bloated /rescue directory.
(Someone correct me if I have the details wrong.) As long as we’re talking about things that would help DragonFly in a larger environment, can someone work on a VM balloon memory driver, too?
If you noticed the lack of a GUI DVD image for the 3.6 release of DragonFly, I posted a followup note on the users@ list that talks about the steps to get X installed. It’s not much work, with pkg set up.
Sepherosa Ziehau has an IPv6 patch for you to try. What’s it do? I think it improves performance under multiple streams of traffic, but that’s from looking at the code and totally guessing.
A recent commit from Sepherosa Ziehau has a 5% improvement in the number of network connections per second a x86_64 machine can accept. He’s also reducing the number of IPIs during network activity. If this seems somewhat esoteric, it’s because network speeds are getting so fast that the benefits come from reducing the accompanying CPU load.
If you’re on DragonFly 3.7, you will need to build world before building the kernel again if you are updating to some point in the last 24 hours. Sascha Wildner points out the related commit.
DragonFly has moved from the old USB stack to USB4BSD by default. That means:
- If you are already using USB4BSD, you will want to remove WANT_USB4BSD from your kernel config.
- If you have trouble, switch back to the old USB.
- There’s some drivers that are not yet converted; help with them would be appreciated.
- A full kernel/world build and ‘make upgrade’ will be needed in either case.
Sascha Wildner’s announcement email has all the gory details, including the kernel config changes to move back to the old USB setup. This is of course in master; 3.6 users are unaffected.
If you are upgrading packages on your DragonFly 3.6 system, and you have docbook installed, there’s an extra step needed because of the moving around of several docbook packages. If you don’t have docbook installed – nothing to see here.
I followed up with Google on why DragonFly isn’t in Summer of Code this year. It is exactly as I suspected: they want to get new organizations in. DragonFly’s been doing it for 6 years, so they are picking new orgs over returning ones. This is apparently the same reason NetBSD isn’t in this year, either.
(Honestly, I can use the break.)
Sascha Wildner has updated arcmsr(4), which brings in support for the Areca ARC1214, ARC1224, ARC1264, ARC1284, and ARC1883 models, from FreeBSD. Please test if you have the appropriate hardware.
Another week where I barely need to look up source code commits.
- PC-BSD Weekly Digest 18 and Digest 19.
- OpenBSD’s signify tool has been backported to OpenBSD versions < 5.5.
- Video of an OpenBSD install.
- xorg, unprivileged on OpenBSD. (via)
- This is a good idea: FreeBSD 10’s release.sh mapped out.
- bcrypt() updates in OpenBSD and what it means for you. (also)
- iXSystem’s NYCBSDCon 2014 recap. (via nycbug-talk)
- A description of those expensive/busy WhatsApp FreeBSD servers. (via)
- FreeBSD and Linux, a comparative analysis. (via #nycbug)
- NetBSD is bringing in BIND 9.10.0b1. (a beta?)
- NetBSD is also in the process of moving from gcc 4.5 to 4.8.
- Yes, You Too Can Be An Evil Network Overlord. I still haven’t set up the Netflow system that I want to set up, dangit.
- pkg will require libucl. This affects FreeBSD and will affect DragonFly too.
- OpenBSD has an experimental USB installer. This may be new to the upcoming release – I don’t know.
Sascha Wildner brought in ACPICA 20140214, and his commit message has a list of the updates.
The DragonFly Mail Agent is being suggested as a possible sendmail replacement for FreeBSD.
I’ve tagged version 3.6.1 of DragonFly, and built ISO/img files of it. They should be available by now on mirrors if you need them, or you can just upgrade as normal. See the linked tag commit message for what’s changed.
Grep /var/run/dmesg.boot for PMM, and if it turns up, Sepherosa Ziehau has a patch he’d like you to try.
If you have i915 chipset-based video on DragonFly, and you get a “Output xxx has no Monitor section” complaint in your xorg logs, look at this fix using xrandr.
As I mentioned on kernel@, I’m going to roll a point release of DragonFly soon. Push in your changes if you want to get them in!
Antonio Huete put together a list of goals for the next release on the DragonFly bugtracker. Some of them are pretty ambitious, some of them are relatively easy, but they are all very useful.
We’ve got Go builders running for DragonFly, but nobody actively maintaining Go itself on DragonFly. The dports version builds, but there’s a Go release coming up and having native support would be much better than relying on chance FreeBSD build compatibility.
The current error as I type this is a TLS problem that sounds like a simple fix, if only I knew where it was.
Here’s a potential DragonFly and Summer of Code project: adding support for more than 63 cores to DragonFly. Matthew Dillon has already outlined how.
There seems to be a lot of ACPI-related updates lately: Sascha Wildner has updated ACPICA in DragonFly to what I think is the very latest version. See his commit for the differences.
John Marino updated daemon(8) on DragonFly. For some reason, I didn’t know it was a standalone program. I knew about the idea of daemons as helpers based inside the computer, which is why so many server programs end with a ‘d’ – sshd, ftpd, and so on. Inexplicably, I never actually saw the program itself.