Tomohiro Kusumi has been quietly making a lot of commits to Hammer. I haven’t been linking them because they don’t necessarily equate to new features, but here’s an recent exception: the -A argument will make your Hammer command run on every PFS. It only affects reblocking/rebalancing – for now.
It’s been a relatively calm week, for once.
- New Delhi has a BSD user group. (via)
- PC-BSD and 4K — Oh my!
- Is nvidia the best option for gaming on FreeBSD?
- EuroBSDCon 2015 has extended the time for paper submission, cause they have so much to work through.
- Hipster keyboard layout on NetBSD
- The pkgsrc-security GPG key has changed.
- Binary packages of pkgsrc-2015Q1 for illumos and OS X are available.
- I like cross–pollination.
- PC-BSD can now restore encrypted volumes over iSCSI.
- Two more mentions of OpenBSD (though any should work) on Vultr.
- Better OpenBSD performance on KVM via x2apic mode.
- OpenBSD rolls their own file(1).
- OpenBSD has W^X support for i386 userland now.
- 2-factor authorization on FreeBSD. (via)
- My switch to OpenBSD, first impressions (via)
- Microsoft .NET Running on FreeBSD 10.1/amd64 (via)
You can now export Hammer slave volumes as NFS mounts – but since slave volumes are updated from master, you’re mounting a snapshot of that point in time. That may actually be an advantage.
DragonFly builds two compilers by default. If you weren’t interesting in building both, there were switches to build only the default, like NO_GCC47. This changed with every compiler update.
With the switch to GCC 5, the new switch is “NO_ALTCOMPILER”. That will last through compiler changes. I’m mentioning this now because sooner or later, you’ll want to gain back some time on a buildworld.
DragonFly now has GCC 5.1 release. If you are running DragonFly master (i.e. 4.1), you’ll probably want to both rebuild world and kernel, and update your packages so they all match. There’s already packages built with GCC 5.1, so binary package upgrades can happen quickly. There’s GCC 4.7 packages still available if you aren’t making the jump yet.
If you’re on DragonFly 4.0.x – nothing’s changed.
Here’s some comments from Matthew Dillon on page coloring in DragonFly; a topic that comes up every year for some reason.
The release candidate for GCC5 (5.1.0) is out, and it’s in DragonFly too. It’s not yet switched over to run as the default – that’ll require the release.
The default compiler in DragonFly is going to change over from GCC 4.7 to GCC 5.x very soon, to match the GCC 5.1 release. This means that packages built for DragonFly-master won’t be compatible with the old ones. You will need to reinstall packages when you next ‘pkg install’. John Marino has an extensive writeup detailing what’s needed, and the actual change is some days off.
If you are using DragonFly 4.0.x (the release), this doesn’t affect you at all.
Francois Tigeot has a new update to the drm/i915 driver for testing. It matches, feature-wise, what’s in Linux 3.12. Try it if you’ve got the hardware. (and dragonfly-master)
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.
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.
- DiscoverBSD for 2015/03/30.
- Lumina 0.8.3 is released.
- Building PC-BSD Utilities From Source. (video)
- BSD Magazine for March.
- Directly building FreeBSD AMI images.
- FreeBSD daily status reports, a little more human-readable.
- 4 new commands in FreeBSD DDB.
- The FreeBSD boot loader can now take your GELI passphrase.
- A probably definitive answer on OpenBSD and clang.
- pf tables mean no reloading.
- BSD contributor Paul Schenkveld has died.
- If you are in the UK, there’s a mini OpenBSD ports hackathon happening now.
- NetBSD systems can now resize / on reboot, if space is available.
- LibreSSL in pkgsrc, soon.
- NYCBUG’s next meeting is April 8th, with Christos Zoulas presenting blacklistd.
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.
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.
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.
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 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.
- Setting up an OpenBSD mail server. (via)
- FreeBSD-current users, regenerate your keys. (fixed)
- Using OpenBSD and vxlan to overlay remote lans. (via)
- A Prediction: 2020 the year of (PC-)BSD on the desktop. (also)
- “Has Linux lost its way?” (via) (also)
- DiscoverBSD news for 2015/02/16.
- Curious if FreeBSD or any other BSD district would work better on a MacBook pro?
- Am I taking a realistic route to learning more about internals? (hey, it’s DragonFly!)
- Speaking of which: cross–pollination.
- More cross-pollination, and surprise from me; I didn’t know USB video link worked on any BSD.
- The m0n0wall project has ended.
- The end of ‘games’ as a separate object on FreeBSD.
- Tetris: still changing.
- autonet – simple automatic wifi chooser on OpenBSD.
- pkgsrc binaries as an exit strategy from systemd.
- IPFW now the default firewall (and on) in PC-BSD.
- The updated roadmap to 1.0.0 for Lumina, PC-BSD’s desktop environment, to go with the 0.8.2 release.
- PC-BSD at SCALE.
- s2k15 hackathon report.
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.
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.
This week is relatively quiet.
- Raspberry Pi GPU acceleration in NetBSD 7. (via)
- OpenBSD networking on Macbook Pro?
- PC-BSD 10.1.1 is out.
- Is there any RNDIS support in any BSD?
- Ask HN: Laptop for FreeBSD?
- Stuck between OpenBSD and DragonFly BSD (mostly Web and File Server)
- devctl, a new device control utility in FreeBSD.
- FreeBSD has gained a VCHI driver for the Broadcom “VideoCore IV GPU”.
- Things you can remove from FreeBSD.
- PC-BSD gains ‘personacrypt’, for encryption of home directories.
- OpenBSD gained iwm(4), for Intel 7260 wifi.
Here’s a number of DragonFly links to clear out my backlog:
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.
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.
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.
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.
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.
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.)
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.