The release candidate for DragonFly 4.0 came out last week, and normally the release would happen after a week. There’s still a few people reporting an odd freeze, so until we can find a cause, we’ll continue to wait.
Chrome runs on DragonFly now, apparently possible now because of this ported fix from Joris Giovannangeli.
Despite my complete lack of good planning, John Marino and Francois Tigeot have packages available for the DragonFly 4.0 release candidate that I assembled. Point at this directory to use them.
Your local mirror should have a copy of the release candidate for DragonFly 4.0.0 by now. Please try it out and report problems. Note that this is a x86_64 only version; there’s no i386 version though you may be able to manually build on i386.
It’s been possible to install and run clang on DragonFly for a long time, of course, and at least build world with it. However, John Marino is putting in significant work to make clang one of the system compilers, replacing the older gcc44 that’s in DragonFly now. (The newer gcc47 stays.) This won’t be part of the next release, but it should be available soon after.
Francois Tigeot gave talks at EuroBSDCon and XDC 2014, and he’s posted slide and video links. He covers DragonFly and Postgres and video drivers, or at least I assume so cause I haven’t watched them yet. There’s other BSD-specific material available too, according to his post.
John Marino updated wpa_supplicant (in dports). He then suggested moving it out of base into dports, so that it could be updated independently of the base system. (this update, for instance, took years.) Since wpa_supplicant is necessary to get some systems online – and it can’t be installed if missing if you don’t have a network link – it may be too risky. I think other packages could be moved out, myself.
The powersaving page on dragonflybsd.org has seen a bunch of updates; this should be handy even if you aren’t on battery power that often.
Markus Pfeiffer has imported FreeBSD’s if_lagg to DragonFly. It’s for talking LACP over multiple network ports, so that the traffic from those multiple ports can be aggregated – if what’s on the other end generally understands LACP. (Failover mode may not count.) Please test if you have that sort of surfeit of network ports.
Matthew Dillon hasn’t committed anything to DragonFly in several days… cause he just got married! Congratulations to the newly married couple.
There’s been so much work in DragonFly recently that makes a desktop easier (i915 support, dports, and so on), that I decided to resurrect an older Dell machine and use it as my desktop.
The Dell that I’m using is a leftover from someone else’s workplace; it’s 7 years old, and has “only” 4G of RAM and a Core 2 DuoE6600 CPU in it. It works, however.
Setting up DragonFly and installing xorg and so on is pretty straightforward. Using dports makes it crazy quick to add all the packages. I went for XFCE4 because I could. Starting X gave me some trouble at first; the default config couldn’t find the mouse and would eventually crash.
Running ‘X -configure’ created a xorg.conf file I could edit, and these lines in /etc/rc.conf gave me a working mouse:
moused_enable="YES" moused_type="auto" moused_port="/dev/ums0"
The crashing problem with my radeon-driven video card was fixed by turning off the acceleration – uncommenting this line in xorg.conf did it:
Video performance isn’t as nice as I would like it with acceleration, but this is an older machine anyway.
I couldn’t get sound working. Francois Tigeot has a branch of DragonFly that contains newer sound drivers brought over from FreeBSD, here:
git://leaf.dragonflybsd.org/~ftigeot/dragonfly.git (pcm_2014_september branch.)
It doesn’t support device cloning, so I can run Youtube videos and XMMS, but not audio from both at the same time. (for instance; not that you’d want to do this other than by accident)
I installed x11/webfonts, and web pages look a bit better after changing my default font preferences.
And… that’s about it. It’s a working desktop. Digging up a half-height video card that has working acceleration is a next step, but I can’t imagine that’ll be expensive. I wish I had done this a long time ago.
Markus Pfeiffer has made it possible to control your laptop’s backlight using ACPI – if you have a i915 chipset and DragonFly. xbacklight does not work, but setting hw.acpi.video.lcd0.brightness does.
In a bit of perfect timing, PC-BSD’s desktop environment, Lumina, has been ported to DragonFly, thanks to mneumann! It’s not in dports yet, but it should be buildable from source…
Why is it so warm out? I want autumn to start.
- BSD compared to Linux, an explanation.
- A description of what rcctl does. (via several places)
- NetBSD runs on the OpenRISK 1000.
- tmux-resurrect, making tmux survive machine restarts.
- OpenBSD version numbering explained.
- PC-BSD has its own subreddit.
- Lumina is now available as a port – will it work on DragonFly? Someone try!
- DiscoverBSD news for 2014/09/01.
- NetBSD 5 systems now use modular xorg.
- The 2014Q3 pkgsrc freeze is coming up.
- PXE installs of OpenBSD with Serva.
- Are you a “connoisseur of old time stamps“?
- FreeBSD has some support for the Altera SOCFPGA.
- Your cross-pollination moment of the week.
- Yes, it runs (Retro)BSD.
This very long commit message from Sepherosa Ziehau details the UDP changes he’s made. It’s mostly technical details, but at the end he mentions this little tidbit:
“For ‘kq_connect_client -u’ test, this commit gives 400% performance improvement (31Kconns/s -> 160Kconns/s).”
If you are on DragonFly, using pf, using altq, and using fairq to control usage, there’s a latency bug that Matthew Dillon recently fixed. He’s posted an announcement and committed fixes to master and 3.8, so it’s only an upgrade away.
You can now start moused with an argument, so it will look at the right device. In most cases, I imagine “
/etc/rc.d/moused start ums0” will be what anyone wants. Credit to Michael Neumann for the update. Perhaps
moused_flags="ums0" will do it too? I haven’t tried yet.
This will overwrite your /etc/devd.conf.
If you are using the ATI Mach64 drm driver on DragonFly, Francois Tigeot would like to know. He’s done something that breaks it, but he’s making the educated guess that this more-than-10-years-old card is no longer in use.
Because of some structure changes made by Matthew Dillon while chasing a pf bug, you will need to do a full buildworld/buildkernel on your next update – if you are running DragonFly-master. 3.8 users are unaffected by the bug or the change.
The server that hosts shiningsilence.com is getting old, and it’s time for me to go to 64-bit DragonFly. It’s audience opinion time: what have you purchased lately, and liked? What would you suggest?
It seems pkg 1.3.6 was slightly scrambled. If you happen to have built and installed it, John Marino has special instructions on how to update to 1.3.7. If you are on DragonFly 3.8, you can follow those instructions now, and if you are on 3.9, that repo should be ready for an update in the next few days.
You should perform a full world and kernel install if on master.
Several people (including me) have been getting bit by a problem: when performing an installworld with a changed kernel, the vn kernel module is loaded, but it was built by the previous kernel and may cause problems when it doesn’t match up.
To fix that, vn is now built in, instead of being a separate module. The rescue initrd (which is what is being mounted when it has this problem) is now installed via a ‘make rescue‘ command that can wait until a successful installworld and reboot.
Another long list. These are making my Friday nights take some extra effort.
- Oolite, an open source game based on Elite. Yes, it runs on BSD. I’m surprised I haven’t posted about it before. (via)
- My Experience Switching from Slackware Linux to FreeBSD.
- A week of pkgsrc, #3.
- DiscoverBSD for 2014/08/18.
- OpenBSD is gaining a rcctl(8) tool for automation.
- Phabricator on FreeBSD installation notes.
- 20 years of FreeBSD ports.
- “Does BSD perform disk caching less aggressively?” I bet the person asking was using two different machines at different times with different loads, which means he doesn’t know what he’s looking for.
- The FreeBSD Foundation’s August Update is out.
- Some people don’t like pkg.
- The EuroBSDCon 2014 travel grant has been extended, and Google has grants to bring more female computer scientists there.
- Spatializer support in NetBSD.
- NetBSD is keeping up with the gpl2 version of GNU Make.
- PC-BSD 10.0.3-RC1 has been tagged.
- FreeBSD has a new automounter.
- FreeBSD has a set of keymap conversion tools. Might be useful to someone?
- FreeBSD now goes up to 256 CPUs. (I thought this already happened?)
- Yay cross-pollination!
- Apparently people don’t pay attention to file contents.
- IPv6 tunneling on OpenBSD.
- OpenBSD has replaced BIND with unbound in the base system.
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.