DragonFly – Page 24 – DragonFly BSD Digest

2019/06/19

5.6.1 tagged and built

Shamelessly copied from my own users@ post: I tagged 5.6.1 and built it earlier today. This version has a corrected sshd_config and fixes a lockup bug in ttm. The ISO should be showing up on mirror-master.dragonflybsd.org in the next 20 minutes or so, or you can rebuild using the normal process on an existing 5.6 system:

cd /usr/src
git pull
make buildworld
make buildkernel
make installkernel
make installworld
make upgrade

If you are still on 5.4 or earlier, you need to bring in 5.6 sources, which is noted in the 5.6.0 announcement.

2019/06/18

5.6.1 on the way

A last-minute drm change in DragonFly 5.6 turned out to cause a reproducible lockup, so there’s changes in place for it. This means 5.6.1 will need to be rolled, which I will do in a day or two. If you want to update now, the normal buildworld/buildkernel process will get you this change.

2019/06/182019/06/17

OPIE removal in DragonFly-master

OPIE was disabled recently in DragonFly. Now that the 5.6 release is out, it has been removed. This may require manual intervention if you are on DragonFly-master (i.e. 5.5. or 5.7) and update in the next day or two. This need to fiddle with it will go away soon with changes to ‘make upgrade’; I will mention it when I see it.

This won’t affect anyone running 5.4 or 5.6. It’s only in development.

2019/06/17

DragonFly 5.6 released!

DragonFly 5.6.0 has been released. This version brings an improved virtual memory system, updates to radeon and ttm, and performance improvements for HAMMER2. Matthew Dillon did some informal testing of the VM improvements, and posted results to the users@ list.

My users@ post has the usual details on upgrading (pay no attention to my 5.4 typo), as do the release notes.

2019/06/142019/06/14

ttm and radeon DRM updates in DragonFly

Francois Tigeot updated ttm and radeon DRM in DragonFly to match what’s in I assume the Linux 3.18 kernel. Please try if you have the appropriate hardware. This was at the start of May, so you may have already done so without realizing if you run -current. It’ll be in the 5.6 release, too.

2019/06/12

DragonFly 5.6rc1 images uploaded

ISO and IMG files of DragonFly 5.6rc1 should start showing up at mirrors over the next few hours. This is the release candidate, not the release, so don’t install unless you want to test.

2019/06/11

DragonFly 5.6 release candidate 1 tagged

This will turn into a real 5.6 release probably by weekend if no problems are found. See the tag commit message for a list of the commits since 5.4.

2019/06/102019/06/07

HAMMER2 and crypto

‘daftaupe‘ has updated the installation page for DragonFly to note what different steps you use when doing a manual install over encrypted HAMMER2.

2019/06/07

New DragonFly subdomain

Thanks to a suggestion from Lassi Kortela, man.dragonflybsd.org now exists and takes you directly to the online man page interface, similar to man.(free/net/open)bsd.org.

2019/06/062019/06/07

vkernel as background process

A question on starting up a virtual kernel on DragonFly and sticking it in the background led to some suggestions – follow the thread.

2019/06/05

Release shrinkage

The next release of DragonFly should be smaller; Sascha Wildner and Rimvydas Jasinskas have removed or substituted enough packages on the installer image to drop the package disk usage 50%.

2019/06/04

DragonFly, mysql, ipv6, and defaults

I am posting this so it can help someone else, someday.

I have a DragonFly-5.4 system. I installed mysql56-server, and started it up. By default, it listens on “*”, which meant it listens on a local socket and IPv6 ::1 – not 127.0.0.1.

2019-06-04 13:35:03 15833 [Note] IPv6 is available.
2019-06-04 13:35:03 15833 [Warning] Failed to reset IPV6_V6ONLY flag (error: 45). The server will listen to IPv6 addresses only.

I put bind_address=127.0.0.1 into my.cnf to get IPv4 loopback to work. Local socket connections still worked either way. I’m not using IPv6 on this machine, so this solution works in this situation. I’m not sure my mysql decides to go only IPv6 based on a strange flag, but mysql is reliably unreliable.

2019/06/03

A bunch of vendor updates

Rimvydas Jasinskas has done the tedious but useful work to update a number of utilities in DragonFly to newer vendor versions: LibreSSL 2.9.1, libarchive 3.3.3, xz 5.2.4, ldns 1.7.0, and OpenSSH 8.0p1.

2019/05/312019/05/30

OPIE out of PAM, other places

opie(4) is no longer an option in several places in DragonFly. It’s also known as S/Key, and I’d be mildly surprised if you’ve used it.

2019/05/30

part-by-label: an additional benefit

Remember the commit that autocreates human-readable disk device names under /dev? (Here’s a reminder.) It’s now in 5.4 – technically, since 5.4.2. Anyway, it will automatically identify the root USB disk when you boot from a USB .img file, so you no longer have to guess which /dev/daX file it was – usually da8 but sometimes you got a surprise instead.

2019/05/29

Bugs no longer automatic

That sounds like a good thing, right? No automatic bugs, just manually placed ones. What it really means is that bugs.dragonflybsd.org no longer autocreates users, cause there was a certain amount of spam coming through freely created accounts there. It may be hard to tell the next step.

2019/05/28

man and groff out, mandoc in

Sascha Wildner has committed mandoc(1) to DragonFly to use for man, whatis, apropos, and other functions. One less GNU utility, and also means groff can come out of the base system. That is almost the last C++ code in base… I am not sure what remains.

2019/05/272019/05/30

vkernels vs pmap

Because of the ongoing pmap work from Matthew Dillon, building vkernels may not work for a short period in DragonFly-master. “A short period” usually means a few days for this sort of thing.

Update: all better now.

2019/05/24

AWS sample file for DragonFly

Here’s something that might be useful: an example cleaning file for creating an AWS DragonFly image. Here’s the blob if you want to see what’s in it. I assume you will want to install awscli to use.

2019/05/22

Major kernel VM pmap work in master

I’m jumping ahead in my very full queue of DragonFly items to post to something new: Matthew Dillon has committed extensive work to the virtual memory system in DragonFly. He has a message to users@ that sums it up.

If that’s not enough reading for you, I’ll point at commits where he reports speed improvements, changes to systat(1), or just 2-decade-old copyright items.