If you are on DragonFly-master and you upgraded during select hours on the 25th of February, you may have been bit by a makefile error. The fix, as listed in that link, is simple:
cp /usr/src/share/mk/sys.mk /usr/share/mk
If you are not on -master or you did not upgrade in that timeframe: never mind.
Michael Neumann has switched out pkgsrc packages for dpkg packages for building DragonFly with a GUI. There’s no built image to download right now, but I’m optimistic the next release will have it. You can build it now on a DragonFly system using src/nrelease. With all this video work going in lately, it will give us something to show.
If you’ve been sitting with a Radeon-based video card and wishing you had all the nice updates i915 users are getting, today is your lucky day. Michael Neumann has brought Radeon support equivalent to Linux 3.9 into DragonFly, and he has a 3.10 branch for testing if you feel adventurous.
There’s some DragonFly material in here, though I normally confine that to the rest of the week. It’s inextricable from the rest of the links.
I admit I never thought about it much, but I’ve also never had enough RAM to matter: there’s a memtemp(4) tool that monitors temperature sensors for your system’s memory. Sepherosa Ziehau has updated it on DragonFly to support some newer processor setups.
This bites many people sooner or later: you think you’ve turned sendmail off, but it still gets opened up on your system. The answer: sendmail_enable=”NONE”.
(It should support sendmail_enable=”NOPE”.)
Several of the DragonFly machines used for building packages and/or releases have SSDs, and have been vigorously exercising those disks for some time. SSDs are supposed to have a shorter lifetime than spindle-based hard drives. However, Matthew Dillon found that there’s surprisingly little wear on those SSDs. This empiric information was noticed in several places.
Well, might rather than will , but I had to make a music reference. There’s a bug in versions of pkg from 1.4.6(ish) to 1.4.11 that can make it accidentally delete itself while updating packages. If this happens to you, there’s an easy fix, as posted to users@:
# cd /usr && make pkg-bootstrap
Once you’re on version 1.4.12+, you’re fine.
Do you have a DragonFly system with a Radeon or i915 video card? There’s updates for the drivers associated with either; you can help out and test them.
Say hello to the newest DragonFly committer: Tomohiro Kusumi. He’s been contributing Hammer patches for some time and appearing on IRC, so it’s easier to just let him make changes directly. Welcome, Tomohiro.
John Marino has removed gcc 4.4 in DragonFly, and replaced it with gcc 5.0. Two things to note: gcc 5 does not yet successfully build world, and DragonFly is an officially supported platform for gcc with this release.
If you have a em(4)/emx(4) card, AKA ‘Intel(R) PRO/1000′, Michael Neumann has an update for you. It’s from Intel’s 7.2.4 release of the code. This is to support the new I218 cards. Initial reports are positive.
This week is relatively quiet.
DragonFly is the only BSD, I think, to switch fully to Git for version control, and Matthew Dillon wrote up how DragonFly uses Git.
Matthew Dillon brought in some wireless networking updates – the ath(4), iwn(4), and wpi(4) drivers are updated. There’s porting notes if you need them, too. In related news, rum(4) is also improved. The updates apparently benefited DragonFly and FreeBSD at the same time.
Francois Tigeot has updated the i915 drivers in DragonFly (remember the call for testing) to match what’s in Linux 3.10, which means you should get excellent accelerated video performance on most any recent Intel video chipset, on DragonFly.
Here’s a number of DragonFly links to clear out my backlog:
If you have very recent alc(4) hardware, it may be supported now. If you are booting over NFS, it may be faster now. These changes are unrelated other than both being recent – NFS is improved for any chipset.
powerd now can be adjusted on DragonFly, for quicker returns to high CPU frequencies, or slower … slowdowns? It’s quickly quick or slowly slow. That’s not the best explanation, but I like rhymes. For a less stupid description, look at the man page, which now includes usage examples.
Francois Tigeot has updated the drm/i915 code again, matching Linux 3.10 for feature level… but it’s a big update. If you are
- Running DragonFly-master
- Using a i915 chipset
- (optional) On a chipset that is not Haswell or Ivy Bridge
… He could use your testing and feedback.
I’m saving up for one of those Acer c720p Chromebooks that people seem to be enjoying. If you have enjoyed the Digest for a long time and want to help, please do. Of course it’s to run DragonFly.
Thanks to the generosity of a bunch of people, I’ll get a C720 and an SSD too. Thank you all very much, people I have never met but would like to shake the hands of.
Matthew Dillon purchased some Haswell-based motherboards, and documented his hardware setup, for anyone who is looking to build a decent, new DragonFly system.
ISO/IMG files for DragonFly 4.0.3 have been uploaded and by now should be available on your favorite mirror. You should update for the OpenSSL upgrade. If you already have DragonFly 4.0.x installed, the normal ‘make buildworld && make buildkernel && make installkernel && make installworld && make upgrade’ cycle should work just fine.
DragonFly 4.0.3 has been tagged; you can look at the tagging message for details, but the major reason for doing so is to include OpenSSL-1.0.1l. I will have images up soon.
John Marino has written up an extensive how-to for slider, the history tool for Hammer filesystems, including screenshots.
Thanks to Sascha Wildner porting from FreeBSD, mixer(8) now remembers state. This is something I’ve wanted for a long time.
For whatever reason, I’ve seen several people in the last week or so have mouse problems on install, and they were often solved by running moused. So, there’s your little reminder.
Can someone with experience on Google Compute Engine try out running DragonFly on it? There’s FreeBSD instructions, so it might work.
DragonFly no longer has SCTP. Nobody minds, I think – I had to look up what it is.
The short answer is ath(4) and iwn(4), via this post. There’s an update coming for the wireless infrastructure in DragonFly; Matthew Dillon and Adrian Chadd (on the FreeBSD side) are working together for improvements.
While I’m mentioning recommendations, the Silicon Image 3132 chipset is apparently excellent for eSATA drives on DragonFly.
Matthew Dillon’s added a sshlockout utility, to temporarily block SSH traffic from repeated brute force SSH login attempts. It’s been mentioned before, but it’s in the system now. It’s been refashioned to work with pf.
Francois Tigeot has performed a major upgrade of DragonFly’s sound system. If you had sound problems or unsupported hardware before, this may fix them. It will require a full buildworld+buildkernel.
Romick posted some more tips on setting up various special keys on an Acer c720 Chromebook, running DragonFly of course, and Matthew Dillon also has backlight key configuration. I wish I had a spare $200 right now for one of these.
I managed to miss this last week because of issues with my RSS feeds, but the 71st episode of BSDNow is/has been up. It’s “systemd isaster”, cause the interview is with Ian Sutton talking about BSD replacements for systemd dependencies. There’s a number of at-least-slightly DragonFly-related things in there, including OPNSense, pkgng, and Hammer mentions.
I’m breaking my normal weekend posting schedule to note that DragonFly 4.0.2 images are now linked on the main site and on mirrors now/soon.
DragonFly 4.0.2 has been tagged. I’m building the release images now. If you’re already running 4.0.1 it’ll be easy enough to upgrade to; you will want to catch up to this commit fixing a quiet memory issue.
The CAM layer in DragonFly has had its big lock removed/been marked MPSAFE, so you will notice a performance increase when using multiple disks. (assuming you aren’t throughput-limited, of course.)
That’s Virtual Private Server, if you don’t know the term. I mentioned VPSs and BSD before in a In Other BSDs article, but “Ed” found an article specifically about installing DragonFly on Vultr.
There’s a FreeBSD Forums thread about ZFS and Hammer, as several people have pointed out to me. It’s interesting to see, but there isn’t a lot of quantitative discussion. (It’s a forum post, not a white paper, though.)
Do you remember the BSDNow story a while ago about a Tanzanian community effort using FreeBSD to build a library? They’re looking at DragonFly, too, because of the low resource requirements. From that discussion: a hardware reason for an ‘indefinite wait buffer’ error, and a note on how to most efficiently download packages for multiple machines.
Sepherosa Ziehau has posted a note that V4-mapped addressing is no longer supported in DragonFly. You will need to do a full buildworld/buildkernel if you are running master. Also, TCP MTU path discovery is on by default. Also also, he’s added a SOL_SOCKET/SO_CPUINT socket option for use to reduce load in heavy network activity. As usual, I don’t quite comprehend.
John Marino has created something very useful: a graphical tool for Hammer file history. It’s called ‘Slider’, and it uses curses to work in a terminal. It shows historic versions of files and can restore those old versions as needed. This was already possible in Hammer, of course, but it required a sequence of commands that were not straight-forward. I’ve been slow enough posting it that version 2.0 is already out, offering a way to see files that no longer exist, but are still in history. (i.e. deleted some time ago) ‘Time Machine’ sounds like the best name, but that seems to be taken.
One way to keep file history on an very active Hammer disk from eating up all the space: more snapshots. This may seem counterproductive, but disk pruning eliminates historical data between snapshots, so you can keep older data at the cost of some temporal accuracy.
As part of another thread, Steve Petrie posted an in-depth description of how and where and why he’s using DragonFly. Worth looking at either for workflow tips or for just seeing the use case.
I sort of lost a day this week because of an accidental 20-hour workday, but I still have the links:
Note: corrected VPS hosting link.
If you really, really want to make sure you aren’t pulling in any parts of X when installing dports, and you’re building from source, there’s a few options you can set to keep X11 off your system. You can even go farther.
I had to type it that way because it rhymes. Sascha Wildner has committed an IPMI driver port, tested/watchdogged by Markus Pfeiffer. What’s it do? It’s a machine management standard.
Get ready for some reading.
It’s possible, if you are several releases (years) behind, to end up with a DragonFly system that can’t compile and install the current release, due to incremental changes over time. It’s rare, but it could happen now between, say, version 3.4 and 4.0. The usual solution would be to incrementally upgrade in order, which is a lot of building and updating. The alternative is the new installworld-force option from Matthew Dillon that forces a new set of binaries into place. Use as a last resort.
If you want to help I/O performance when DragonFly is virtualized, here’s a short checklist of what to work on. I haven’t noticed any problems – but I’m not taxing any of my VMs that heavily.
bycn82’s rewrite of IPFW2 is available as a git branch to try out; he’s posted the link. Please try, especially if you are still working with the original ipfw.
(note: remember, ‘ipfw’ in DragonFly is what was called ‘ipfw2′ years and years ago because it was a replacement of the original ‘ipfw’ in FreeBSD. It was called ipfw2 but referenced as ipfw so that the same commands worked. Technically, this branch bycn82 is working on would be ipfw3, but he keeps referring to it as ipfw2. Confused? Good.)
If you’re using one of those Acer C720 or C720p Chromebooks with DragonFly, remember to set:
To automatically enter the right power-saving states on the CPU. You used to have to do it manually, and now you don’t.
Sascha Wilder ported over the urio(4) driver to DragonFly. It’s for the USB-based Rio mp3 players. Does anyone have one of these and is running DragonFly? That would be a startling coincidence.
I have been building up quite the variety this week.
- Bitrig 1.0 has been released.
- Writing NetBSD Sound Drivers in Haskell. (PDF, via)
- ruBSD 2014, happening December 13th in Moscow. (via)
- How to configure full disk encryption in PC-BSD 10.1. (via)
- BSD Magazine for November 2014. (via) Why don’t they put new issue announcements in their RSS?
- A week of pkgsrc #5.
- FreeBSD Foundation’s 2014 year-end fundraising.
- FreeBSD Mastery: Storage Essentials is hitting the printers. There’s a quiet mention of the next two books in that series, too.
- Two new kernel errata for OpenBSD.
- BSDCan 2015 (June 2015) has opened up its call for papers, now through Jan 19th, 2015. (via)
- A conversation about UTF-8, Unicode, and file systems.
- A conversation about random vs. phrase passwords.
- New Directions in Operating Systems conference notes. Lots of BSD stuff in there. (via)
- nih-0.13.0 is out for pkgsrc.
- BSD presentations (including DragonFly) at the X Developers Conference. I mentioned the event itself before, but that link wasn’t open to non-subscribers until later, as pointed out to me.
- Coreboot on the BSDs.
- More talk about embedded OpenBSD on cheap machines, including thin client machines repurposed into routers.
- Noticed in that previous link: <$100 Ubuquiti EdgeRouter-Lites can run OpenBSD? FreeBSD too, apparently.
- Is it time to give BSDs a try?
- Fixing PC-BSD upgrade issues.
This page, Varialus et Anisoptera, set up by… I’m not sure of the real name but it’s ‘varialus’ on IRC – has a detailed description of the DragonFly install process and installation of MATE, plus extra notes. I always find these sorts of cheatsheets entertaining.
The DragonFly boot menu has been cleaned up a bit, and Fred, the dragonfly drawn on DragonFly, is now in better color. In fact, there’s even an option to turn him blue.
Update: I wanted to see what this looked like, and I realized screenshots might help everyone else.
In an effort to reduce my backlog of DragonFly things to post about, here’s quick notes:
I’m running behind so this is a bit old, but: Matthew Dillon commited svc(8), a service manager program. Take a look at its man page to see the potential uses.
Robin Hahling wants feedback on where to go in DragonFly with rcrun(8), service(8), and similar commands. Follow the thread to see the various opinions.
Predrag Punosevac posted his writeup of using LDAP and DragonFly, which I’m noting here for the next person that needs LDAP authentication.
With a recent commit from Sascha Wildner, DragonFly now loads XHCI (meaning USB3) by default. If you had previously tried to install DragonFly via USB stick, and it inexplicably refused to mou t the installer drive… It may work much better now.
There’s an extended article about the DragonFly 4.0 release on linuxfr.org. You need to be able to read French to enjoy it fully, or perhaps through translation, but it goes into some good depth.
The 4.0 release of DragonFly is out! Quoting from the release page:
Version 4 of DragonFly brings Haswell graphics support, 3D acceleration, and improved performance in extremely high-traffic networks. DragonFly now supports up to 256 CPUs, Haswell graphics (i915), concurrent pf operation, and a variety of other devices.
The more eagle-eyed downloader will notice it’s version 4.0.1, not 4.0.0. That’s because
nobody trusts .0 releases I tagged 4.0.0 just before a few useful commits went in, and it’s better to retag to make sure everyone got them. See also my message to kernel@/users@
I’m working on the 4.0 release, but in the meantime, I wanted to point at a slew of updates from Sascha Wildner: ACPICA 20141107, pciconf(8), axge(4), and the kernel part of the netgraph7 Bluetooth stack.
I hadn’t caught this yet cause I am working extra hours, but Matthias did: Matthew Dillon talks about DragonFly and the 4.0 release for a good 43 minutes on BSDTalk.
A fellow whom I’ve only seen named as Bill is working on what he calls ipfw2, though technically what’s already in DragonFly is ipfw2, since it’s the second version of ipfw. Either way, he has a project page up describing what he’s done so far, and what he plans.
Sascha Wildner has removed the old USB system from DragonFly; you’re getting USB4BSD no matter what now, after the 4.0 release. While we’re at it, xhci is now automatically loaded in the installer, so installer USB drives attached to USB3 ports will work.
Markus Pfeiffer has made usb_pf work on DragonFly, which means it’s possible to dump USB traffic and filter it, similar to tcpdump. This can be handy when debugging a USB device, and that’s like 90% of all devices anyway.
If you look at your local DragonFly mirror, you’ll see ISO and IMG versions of DragonFly 4.0.0RC3. Please run, break, and report.
(Check the iso-images directory.)
Imre Vadaz’s recent change to dev/drm, adding kqueue support, has (from anecdotal reports in IRC) made video performance much better. It’s committed to DragonFly 4.0, so it’ll be in the next release.
Matthew Dillon had some followup commits that went in just after I tagged RC2 of DragonFly 4.0 last night, so I’ve tagged RC3. Tagging’s cheap, anyway.
I just tagged a second release candidate of DragonFly 4. Matthew Dillon’s recent reapctl() addtions – now called procctl() – just went in.
Matthew Dillon’s added the reapctl() call, which gives a process control over all sub-processes, even when detached. This is initally useful for bulk builds of dports, but can probably be extended farther…
I said “USB ethernet drivers should work now” yesterday, but didn’t specify what works with the new USB structure in DragonFly. Sascha has fixed that by explicitly porting aue(4), cue(4), ipheth(4) and kue(4) from FreeBSD. As his commit notes, there’s still a few more devices to go.
If you’ve got a USB Ethernet device on DragonFly, it should work. Also, some cell phones tether correctly now, when they may have had trouble before.
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.
If you can read French, or can translate, here’s an article covering the use of DragonFly as a desktop system.