I have had trouble with my daily/weekly periodic reports never making it to my GMail account. Sascha Wildner pointed out to me that periodic.conf has its own answer already:
… and newsyslog is already set to take care of them. There’s more in the periodic.conf man page.
There’s been some linking to the updated HAMMER2 design document. The Reddit link doesn’t have anything specific, but the Hacker News one has some details (including a credit code!) for installing DragonFly on a Vultr VPS.
The most recent (well, this is the mostest recent) update of ACPICA for DragonFly, by Sascha Wildner, is different from the usual import: it happens to include actual upstream support for DragonFly
This week’s BSDNow talks with Baptiste Daroussin about developing and using pkg, for ports and for packaging the base FreeBSD system. (Baptiste has been seen on #dragonflybsd, since pkg is on DragonFly, so I’m sure there’s some relevant bits there, too.) There’s also the usual news summary.
I haven’t been drawing enough attention to it, but there’s been a bunch of HAMMER filesystem activity lately: First, Tomohiro Kusumi has been working on HAMMER – these posts are a small subset of his commits. Second, Matthew Dillon has been working full steam ahead on HAMMER2. The HAMMER2 design document has been updated (read this!), and he’s already accomplished master->slave disk syncing.
It’s not ready for production, of course, which you may already realize, so don’t install it unless you want to work on the code.
If you’re part of a BSD user group, please let me know your schedule. I’m able to catch NYCBUG announcements cause I’m on their announce@ mailing list – but I could use more.
Do you use info pages? Yeah, me neither. John Marino’s removed or converted the various info pages already in DragonFly, and removed texinfo since it’s no longer required. (I’ve linked to a few examples, but there were a number more commits than this.)
The default .cshrc in DragonFly has had some changes, which shouldn’t be anything but handy… assuming you are using tcsh. Also: the loader menu defaults to a blue Fred, now.
In the process of committing binutils 2.25 to DragonFly, John Marino also broke its build into parallel parts and removed the build of the gold linker. Buildworlds should be noticeably faster now, though I don’t have a before/after.
John Marino’s written an extensive page about wireless and DragonFly, on dragonflybsd.org.
If you’re looking to change your DragonFly system’s keymapping to support a non-US character set, use this users@ post from Adolf Augustin as a cheat sheet to make all the right changes.
Matthew Dillon answered some mailing list questions on how clustering and data copies will work in HAMMER2 – no due date, of course, because this is very complex. If you’re really into it, there’s always watching the recent commits.
Matthew Dillon has rewritten the Locking and Synchronization documentation for DragonFly. Keep this in mind the next time you say “Which lock should I use for this new software/ported software?” There’s also locking(9).
The other day, I updated some packages using pkg. The default version of PHP went from 5.4 to 5.6. I ended up doing what /usr/dports/UPGRADING says and making a list of all PHP packages on my system, before removing PHP and its dependencies. I then reinstalled the packages that used PHP, bringing the needed packages back in at the right version. pkg 1.4 didn’t handle the transition cleanly, unfortunately. I also had to specify mod_php56 because pkg was trying to get the 5.4 version despite it not being default.
None of these are insurmountable problems, but it never hurts to be forewarned. pkg 1.5 is on the horizon and may have an easier time with sorting these types of dependency/version changes. This may apply to FreeBSD in addition to DragonFly.
I’ve tagged version 4.0.5 of DragonFly, and it’s available at your nearest mirror. This revision is mostly to incorporate the newest OpenSSL security bump.
OpenSSL has yet another security update, and Sascha Wildner has added it to DragonFly. It probably justifies a 4.0.5 release, so I’ll be working on that.
As a side effect of the new ipfw3 import, the sshlockout script included with DragonFly now has -pf and -ipfw options.
Some recent users threads pointed at SSD wear stats, along with what Matthew Dillon has seen on dragonflybsd.org machines, and good filesystem books.
Bill Yuan’s work on a new ipfw has been committed, and for clarity, called “ipfw3“.
Next time you’re building or installing world on your DragonFly system (running master), your computer will do a better job letting you know the status.
Matthew Dillon pulled in a new USB update from FreeBSD to DragonFly. What does it change? I’m not completely sure, but he did it to get apcupsd working, so that may be a hint.
If you have a HDMI-connected monitor, but no sound, this trick about increasing available memory may help.
DragonFly 4.0 has had a minor point release, to 4.0.4. There was a bug in the initial install where the rescue image installed on disk would be incorrect. This was fixed after the first time a build/installworld was done, but might as well have it start out right. There’s some other small fixes, and the release commit will show you the summary. Download from your nearest mirror or update normally.
John Marino has removed Sendmail from DragonFly (as part of the base system), and replaced it with DMA, the DragonFly Mail Agent. If you just need delivery to local users, DMA will do the trick.
The announcement message covers what you need to do to deal with it (potentially nothing), and there’s more in-depth documentation to cover how to switch if you need more full-featured software.
The newest BSDNow episode talks with Sean Bruno about poudriere and QEMU. He’s using those tools on FreeBSD, but poudriere is useful for building dports on DragonFly, too. The usual news collection is there, too.
If you’re monitoring your DragonFly systems with Nagios, here’s a way to check the health of your Hammer mirror-streams. Thanks, Mike!
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 dports 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.)