Two minor things that were keeping me from mounting Windows shares on boot of my DragonFly system: the right location for nsmb.conf and using proper capitalization. I’m writing it here to save someone else 10 minutes of search.
Some time back, Ján Su?an fixed up some firmware issues on DragonFly. He’s published a first stab at attaching firmware information to files; it’s up for review now and he’d like feedback. Please tell him what you think, if you’re interested in this topic.
‘mazocomp’ has updated the DragonFly mirrors list to include HTTPS links where appropriate, which would be most everywhere. An excellent idea.
While I’m talking about mirrors, there’s some new DPorts pkg mirrors too.
If you were having trouble booting a DragonFly installer – or rather, you could boot but never find a disk to install on, this commit adding support for Sunrise Point, Lewisburg, Union Point, and Cavium ThunderX chipsets may fix your issue.
If you have a lot of RAM on your DragonFly system, there’s a patch that you may find useful. If you weren’t able to install that system, well, there’s another potential fix out there.
If you’d like to set a particular sysctl(8), you enter it into /etc/sysctl.conf. A common mistake is to copy the command line and put “sysctl foo=bar” in sysctl.conf instead of “foo=bar”. This used to cause a warning, but it still bit people, as it would cause a long stream of error messages during boot – with no clear reason, as the kernel tried to understand the command. Now, that typo is handled automatically.
Two links I yoinked from conversation in EFNet #dragonflybsd: there’s a “powersave” power management page on dragonflybsd.org that for some reason wasn’t linked in the main documentation page. I fixed that, and you may want to look at it and change your mwait settings, or look at the corepower(4) module. (From ivadasz’s comments; thanks!)
There’s also an older page on DragonFly and grub2 that may be interesting to anyone looking to boot. (From aly’s comments; thanks!)
I usually get all happy when I see sharing happen across BSDs, and note it here. Here’s an unexpected one: between DragonFly and Haiku.
On your next DragonFly upgrade, watch the end of your ‘make upgrade’ output. You may have some deprecated files, especially if your system has been upgraded through several releases.
= You have 11 now deprecated files.
= Once you are sure that none of your third party (ports or local)
= software are still using them, rerun with REMOVE_DEPRECATED set.
The now-deprecated files will be listed just before this warning. They aren’t removed automatically in case there’s installed software still linking to them. If you are running only dports software, and are up to date with all of it, you are probably fine to remove these files:
make -DREMOVE_DEPRECATED upgrade
If you have software you compiled yourself some time ago, it may have linked to these old files. One way to search for that would be to use find to find all executable files that are in particular directories, and then use ldd to see what shared libraries are used by each executable:
find /usr/local/bin /usr/local/sbin -type f -perm +a+x -print -exec ldd {} \;
… and then grep for the names of the deprecated files. You’ll get a bunch of “not a dynamic executable” errors when you do this because it’s a rough example I did for this post, but you can always pipe the stdout of the command to a file and review later. If you do turn up any executables linked to the deprecated files – recompile!
(If you have a better find string or strategy, please comment.)
Eerielinux has a new Ravenports article: Ravenports explained: Why not just join XYZ? I am linking it now because it’s DragonFly related, but it does touch on all the BSDs. It reviews the reasons for Ravenports – and its competitive advantages, if you look at it a certain way. It’s a followup to the Ravenports update and review linked here previously.
DragonFly 5.4.1 is out, just in time for Christmas. My users@ post describes upgrading, as do the 5.4 release notes. The changes in this version are in the tag commit, which can be summed up as “keyboard fix, dhcpcd support, HAMMER2 improvement”.
Images are available for download at various mirrors, too. If you’ve recently upgraded to 5.4, it’s the normal build process.
I had a lot of tabs to close, if you can’t tell.
- ClonOS 18.12 BETA1. I didn’t know this existed.
- Next NYCBUG meeting: January 2, with a presentation on OpenBSD from Brian Callahan.
- FOSSJobs. I don’t like the acronym, but I’m not going to complain if it gets someone good work. (via)
- Running NetBSD on DEC VAX on SIMH on Raspberry Pi. Video. (via)
- The Future of ZFS in FreeBSD. (Via many places) I don’t like the notion that the BSD implementation of ZFS is now going to be at the very best, only equal to what’s on Linux. That makes it no longer a compelling choice.
- OpenBSD song 6.2: A 3 line diff. (via)
- OpenRC on FreeBSD. (via)
- FreeNAS 11.2 out. (via)
- Related: December FreeNAS Plugins Updates.
- SoloBSD 12-STABLE.
- Stable release: HardenedBSD-stable 12-STABLE v1200058. (via)
- OpenBSD Errata: December 22nd, 2018 (pcbopts). (via)
- Grafana + InfluxDB fun on DragonFly BSD. Okay okay not other BSD.
- Problem booting after upgrading to [DragonFly] 5.4. The story has a happy ending.
- The Super Capsicumizer 9000. (via)
- What are you using for a simple GUI TextEdit/Notepad? The usual suspects of nvi/emacs show up, but there’s a lot more options listed.
- Reducing the delta with upstream version of sanitizers. (via)
- Python Development on BSD.
- Using the GOG.com installers for Linux, on NetBSD. (via)
- Torchlight 2 on NetBSD *almost* works!
- NetBSD desktop pt.5: automounting with Berkeley am-utils. (via)
- Valuable News – 2018/12/14, Valuable News – 2018/12/21.
- Standards. “There is no standard version of the tar program.” Linked with early BSD history, of course. (via)
- telnet, still being a problem. (via)
- protectli router.
- de facto vs de jure maintenance.
- The NetBSD support update before the LLVM-8.0 branching point. (via)
I like seeing someone’s install notes – in this case, DragonFly, followed by XFCE and MATE. You can tell what someone considers the most important packages, cause they always come first. There’s video too. (via)
As planned, there will be a 5.4. 1 release for DragonFly. Matthew Dillon’s work on HAMMER2 will be in there, as will be a fix for keyboard attachment and updates from Aaron LI on dhcpcd support. I will tag and build this weekend, so it’ll be just in time for Christmas.
I didn’t get a chance to mention this before release: script(1) has had a refresh, now sharing more options with the FreeBSD version. The update is in DragonFly-master and in the 5.4 release.
If you happen to have a Intel Centrino advanced 6035 wireless card, it now works on DragonFly, thanks to Tobias Heilig.
This week’s BSD Now covers assembly on OpenBSD, games on FreeBSD, and disk space on DragonFly.
I uploaded the current 5.4 release candidate – there’s an ISO and an IMG file, though your local mirror may be a better place to get it than those links. Or just wait; I think the release won’t be long.
Note that I was smart for once and named it ‘rc1’, so if there’s another release candidate, it can be named ‘rc2’. I used ‘rc’ in previous releases and was never sure if I should name a second candidate rc1, rc2…