DragonFly’s using pkg 1.3, at least on master, and I’ve seen a few people report an error message when performing ‘pkg upgrade’. The error message usually includes something like:
pkg: need to re-create repo Avalon to upgrade schema vers
If you get this, do ‘pkg update -f’ and it will complete.
DragonFly’s dhclient will now retry failed interfaces and handle being re-run gracefully. This is a blessing for anyone who has had a flaky link. Matthew Dillon’s made two other improvements for booting that will also improve boot time when networks go missing.
Here’s a nice advantage for dports and DragonFly: since it’s an overlay on FreeBSD ports, it’s possible to move to newer or different versions of software without waiting for it to happen in FreeBSD. For example: there’s a newer version of the xorg intel driver now in dports – newer than what’s in ports.
If you are tracking DragonFly master, your next kernel build should be full, not quick.
If you have a DragonFly system with an iwn wireless chipset, and you are having trouble connecting and running in the 5Ghz part of the spectrum only, here’s a tip: the -ht switch may fix it.
There’s been good progress in Francois Tigeot’s work on Haswell graphics support in DragonFly. If you have one of those newer units, you should be able to use the i915 driver with it now – as long as you keep acceleration off. (You won’t notice any difference in 2D anyway.)
If you have a i915 video chipset (which appears to be most every recent laptop), Francois Tigeot would like you to try his huge patch. It doesn’t support Haswell chips yet, though it lays some of the groundwork for it.
A frequent question people ask when trying Hammer is “How can I do software RAID to cover a disk failure?” Hammer provides for streaming one volume to another, so you can duplicate drives, but there isn’t an automatic failover mechanism as there is with a RAID setup. The first answer is usually “get hardware RAID“; my preferred solution. The remaining software solutions are vinum, ccd, and lvm for DragonFly.
Thanks to Zachary Crownover, rcreload is available in DragonFly. (It’s always good to see a new contributor name.)
Nuno Antunes brought in a significant number of fixes for libradius. He’s been doing other work recently on netgraph7 support, so I’m linking to this as a ‘signpost’ commit.
If you were looking for something to do, finishing Francois Tigeot’s sound update would help a lot of people. He’s currently tied up with i915 support work. The patches need device cloning to work with devfs, and midi removal.
Tethering now works via the urndis(4) device, from a patch contributed by Sascha Wildner/tested by Yellow Rabbit.
(Updated for correct attribution)
While Matthew Dillon was testing the new up-to-256-processor support for DragonFly, he added a few sysctls, one of which helps qemu performance when emulating a lot of processors. I note it here in case it’s helpful to someone else.
DRM (Direct Rendering, not Digital Rights) on DragonFly will normally eat all the memory it thinks it needs. However, vm.dma_reserved can now be set to a fixed limit in /boot/loader.conf. By default, vm.dma_reserved on DragonFly is set to 16M, and can be set higher. I think this is necessary when running higher-resolution screens… Don’t quote me on that, though.
Francois Tigeot has been working on making i915 video support work better; with his latest update, it’s worth trying the Intel-specific driver instead of vesa if you have both the 915 chipset and are running X.
Matthew Dillon changed powerd on DragonFly so that the system is set to max performance if powerd is killed. Now you’ll know why your fans turned on!
Finally, a much more eventful week. I already noted LibreSSL’s release.
- DiscoverBSD’s news summary for 2014/07/07.
- PC-BSD Digest 31 – there’s now a PC-BSD IRC channel.
- Your server can probably tell you the temperature.
- Future of pf in FreeBSD? Follow the thread. (via)
- DragonFly’s pf alterations discussed for OpenBSD. It wouldn’t be easy without some of the underlying DragonFly architecture, but something for everyone to remember: Henning Brauer is generous with his time and will help people updating pf.
- mfiutil on FreeBSD.
- ia64 processor support is gone from FreeBSD.
- NetBSD now has BIND 9.10.0-P2.
- FreeBSD now has bmake-20140620.
- OpenBSD now has lynx 2.8.8rel2.
- OpenBSD’s relayd now has a new filter language.
- pkgsrc 2014Q2 binaries are out now for several platforms.
- FreeBSD has a new core team.
- More cross-pollination – also from Android?
- OpenBSD-current users will need to update their kernel.
If you’re looking to use LDAP on DragonFly, follow this thread (read the first, keep going) as people talk about implementing it, what they installed, etc. I haven’t tried it myself, yet.
The mfi(4) driver has had some data corruption problems on “Thunderbird” series RAID controllers. There’s a newer driver, mrsas(4), that replaces mfi(4) for these controllers and does not have these issues, but switching may mean new drive locations and therefore some work to get booting correctly again. Sascha Wildner has an extensive writeup about what this entails, and how to switch now if you have that hardware (recommended).
Another ‘quiet’ week – lots of commit activity in the other BSDs, but not a lot to point at directly.
- PostgreSQL/FreeBSD performance and scalability on a 40-core machine. (PDF link, via) There’s comparison to DragonFly’s results, mentioned here before. DragonFly’s solution of shared page tables is dismissed because it would require work to do, though I think that’s a symptom of FreeBSD’s more complex locking model rather than complexity of what’s in DragonFly.
- pkgsrc-2014Q2 is out.
- Here’s some notes on the systemd compatibility GSoC/OpenBSD project.
- The FreeBSD ixgbe(4) driver understands RSS, and so does igb(4).
- FreeBSD GENERIC kernels can now use vt(4), the replacements for syscons.
- FreeBSD images can now boot UEFI.
- FreeBSD 9/10 users using the WITH_NEW_XORG option have a temporary binary ports repository to use, to handle the change in the drivers.
Matthew Dillon changed the default keep-policy in DragonFly to:
set keep-policy keep state (pickups, sloppy)
This is to match other BSDs (which? I don’t know) and reduce overhead, according to the commit.
A note for everyone: use Hammer default on a very busy filesystem, and you will eat a lot of disk space since all file changes are recorded. (I’ve done this to myself a few times.) Francois Tigeot has a list of tips on how to keep that from happening.
The max number of CPUs on DragonFly just went from 63 to 64. This is really just a side effect of preparation to move up that limit, but I am entertained by the single-digit bump.
If you are upgrading a DragonFly 3.6 system to 3.8, make sure you have the absolute latest version of 3.6 first. A few people have had a crash during install of the new initrd, which leaves the system in an unbootable state.
(Why, yes, that is why shiningsilence.com was down for some hours today… With Matthew Dillon and Sascha Wildner’s help, I was able to copy bits of /boot and /usr from a live CD back on disk and get online again.)
Did you try to install DragonFly relatively recently and it never made it past the bootloader? Apparently there’s a bug in some BIOS when using a smaller USB drive to install. The loader checks multiple places for information, and if it checks somewhere that’s ‘farther’ than the end of the disk (i.e. 6G on a 4G USB key), the machine locks up.
Matthew Dillon and Kyle Davis spent a good number of hours figuring this out today, and Matt committed a fix. So, if you were bit by this problem, try a -LATEST image about 24 hours from now and see if it works.
I have a backlog from stuff I missed last week while traveling, so we all benefit!
- PC-BSD 10.0.2-RC2 is out.
- PC-BSD will be at SouthEast LinuxFest.
- Here’s the roadmap for Lumina, PC-BSD’s new desktop environment.
- DiscoverBSD’s summary for 2014/06/16.
- FreeNAS vs. NAS4Free. Didn’t need to be 8 pages. (via)
- Peter’s pf tutorial is very popular.
- The freeze for pkgsrc-2014Q2 has started. (I’m a bit late on this one.)
- pkgsrc has a new Pkgsrc Management Committee.
- This thread, “Best pdf viewer in pkgsrc?” may be useful even if you aren’t on pkgsrc.
- NetBSD gained vmx(4) from OpenBSD.
- NetBSD now has pigz 2.3.1, which apparently stands for ‘parallel gzip‘.
- Here’s one OpenBSD/GSoC project status update; I haven’t seen others.
- Another OpenBSD desktop project started.
- BoringSSL. (via) Already, benefits.
- Ways to test pf.
- FreeBSD/gnats has gone away, and none too soon.
- Again, I love to see cross–pollination.
- The July and August NYCBUG meetings: timekeeping and OpenBSD ports. Here’s some notes on what to expect for the August meeting.
The dports binary packages built for DragonFly 3.4 are removed. If you have a 3.4 system, you can build from source, or preferably just upgrade. Note that the 3.4 release images are still out there if needed.
I tagged DragonFly 3.6.3, at Sascha Wildner’s suggestion. Why do that when there’s a 3.8.1 out? This way there’s a version of 3.6 that has all the fixes included, including the recent OpenSSL updates. This ‘final versioning’ should probably be done for every release. I’ll work on final images.
The 3.8.1 tag was planned for tonight; I’m waiting to find out if there needs to be a new set of binary ports for 3.8.1 before I tag.
I tagged DragonFly 3.8.1; you can see a list of the changes in the tag message. New images are built. If you are already running 3.8.0, a normal
make src-update and rebuild will get you everything.
Sascha Wildner has added the mrsas(4) driver, which works on a variety of LSI Thunderbolt devices – a variety of RAID cards, names for which are listed in the commit message. Note that as of right now, these devices by default get taken by the mfi(4) driver, so you need to take extra steps to get mrsas(4) used.
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.