There’s a minor update for DragonFly 4.2 – this covers a problem with i915 support, so it’s worth upgrading if you have an Intel video chipset.
If you wanted to try IPFW3 and NAT, nans_nans1 has done the experimentation for you, and wrote down the steps.
Now that DragonFly can (in most cases) offer video outside of X with KMS, not just text, more console options are possible. By default, your accelerated console will scale to 80×25, but you can now tell it how many columns you want and it’ll automatically scale to fit your resolution. Or you can turn it off.
Thanks to Sepherosa Ziehau, powerd will now start the shutdown process if you are down to 2% battery on your DragonFly laptop. It also will delay for 60 seconds if you just booted up and are desperately searching for a power cable.
I’ve uploaded DragonFly 4.0.6 ISO and .img files. (Does that capitalization make sense?) They should be available at your nearest mirror, or will be shortly. I am still working on the 4.2 release candidate images.
The more eagle-eyed may have noticed a branching for DragonFly 4.2, and for DragonFly 4.0.6. The 4.2 branch is currently only a release candidate, so don’t necessarily change over yet – it’s for testing, not release.
Note that packages for 4.2 are not yet built, so you’ll have to manually specify a package path to install with pkg on 4.2 – for now.. That won’t be the case for the actual release, of course. DragonFly 4.3 users will have to specify PKG_PATH manually to use 4.2 images until new ones are built. 4.2 release candidate users will be fine. (see comments for correction.)
The 4.0.6 release is mostly to get the recent OpenSSL update into a 4.0.x build.
I am working on image building for both.
This week’s BSDNow has a talk with DragonFly’s very own Sepherosa Ziehau, about the huge amount of work he’s done on the network stack.
Matthew Dillon’s already using a 4K monitor on DragonFly, and he’s written notes on the various performance tweaks that went with it.
The direct memory access reservation on DragonFly has been set to 128M. It used to be 16, but anyone using a system for more than a text console would want the greater memory reservation. It can be set back to 16M, which is useful probably if you are one of those text console users, or if you have a strangely underpowered video card.
Even sysctl accesses can be made to handle multiprocessor environments. This can actually make a difference when you’ve got a lot of processors building a lot of software, as in all of dports.
Those changes I mentioned yesterday for text console support? They’re in DragonFly-master now, along with a loader tunable to turn it on and off.
If you are using a DragonFly system with accelerated video, and you have noticed that you can’t return to a text console after exiting xorg – Sascha Wildner/Imre Vadasz have a branch for you to try. Please do so if you have time and are on master; this is the last big item to fix before the next release.
You can now get temperature readings from your Radeon card under DragonFly.
A short but more interesting list this week, I think.
- ZFS Mastery is out in print and electronic versions.
- BSD management with Puppet.
- DiscoverBSD for 2015/05/25.
- Dell Networking OS 9 powered by NetBSD.
- Lumina Desktop Status Update/FAQ.
- PC-BSD 10.1.2: an Interview with Kris Moore.
- A FreeBSD Foundation visit to the (a?) NYI datacenter.
- “Patrol Read” support in OpenBSD.
- syslog-ng and ELK on OpenBSD.
- Yay for compatibility!
- The Linuxulator on FreeBSD now does 1:1 threads and x86_64.
- See this “Low Cost 10G Router” post on NANOG? Follow the very long thread, and you’ll notice a reoccurring theme: set up a BSD machine.
- Bitrig at NYCBUG on 2015/05/06, video.
Your Not BSD link of the week: Never fix anything.
There’s a new ‘ifconsole’ option for /etc/ttys on DragonFly that may help you if your serial output device is a bit strange.
If you were running a version of DragonFly 4.1 (i.e. the master version, not release) built between the 20th and 25th, rebuild. There’s a UFS bug introduced in that short timeframe.
If you are running 4.0.x release or built your version of DragonFly-master outside of that date range – you are unaffected.
A recent commit from Matthew Dillon means users of Intel Haswell or later CPUs will see reduced power usage, if I’m reading this commit correctly.
Hammer will perform daily housekeeping tasks each night. If you’re up late enough, it may kick off while you are working. If you want to stop the process after it’s already started (since it’s disk-intensive), John Marino has added the ‘abort-cleanup‘ command.
Sepherosa Ziehau has introduced a new sysctl:
Set this to zero and you won’t get endless ARP events from networks you aren’t on. For example, I’m hooked up to a cable modem. I only get a public routable IP address, but the network used for the cable modem network itself bleeds ARP packets out where my DragonFly machine can see it. Since it’s on a different network segment than the address I receive through DHCP, it always fails and the system logs it. For example:
May 11 05:20:52 www kernel: arplookup 100.68.112.145 failed: host is not on local network
I can’t do much about it since that layer 2 leakiness is going to happen, but I can shut it up with this sysctl – and thank goodness, cause I’ve been seeing these messages since first using a DOCSIS modem in… 2001 or so?
Francois Tigeot has committed his Broadwell work, which has a longer-than-I-realized list of benefits. Does anyone have a 4k screen to try?
If you’re running DragonFly-master and you have an Intel video chipset, Francois Tigeot has an update for you. It brings accelerated Intel video up to match the Linux 3.14 version, adds Broadwell chipset support, and should generally improve performance. He lists how to test right in the message.
DragonFly committer Joris Giovannangeli has a Google Summer of Code project. He’s bringing Hammer2 to OpenBSD, in single-node form. It’s a very difficult project, but Joris is a very talented worker.
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.