A tip that might be useful for some readers: Mohammad BadieZadegan posted that he had a poor network connection, and so was having a hard time installing packages. If that bites you too, there are some pkg.conf options – starting with FETCH_TIMEOUT and FETCH_RETRY – that may help.
Rimvydas Jasinskas posted an extended description of what’s happening with dports. There’s a significant xorg reformatting coming in ports, which is going to be absorbed into dports, but it may take some time. There’s also an odd loss of commit rights for John Marino, who commits (frequently!) to both DragonFly and FreeBSD. (His followup) This all translates to some upcoming transition time for dports to accommodate these changes.
Note that if you are using dports binaries, especially on DragonFly 4.6 release, this won’t really affect you; the way dports is set up, binary sets always work. It is interesting to hear about future work, in any case.
This is a minor thing, but I bet someone will find it useful: Chromium in dports has been patched to remove the forced dependency on dbus, which will be useful to anyone using DragonFly and a ‘lighter’ window manager. You still need to specify this preference in your make.conf to have it happen.
Oddball links for BSD this week – but pay attention to the first one.
- Get a BSD person into ARIN. Useful.
- “Any experience with OPNsense?“
- Unknown Horizons: An open-source 2D realtime strategy game. Linked cause it exists as a FreeBSD port and in theory could as a dport.
- We Surprised The Register.
- Looking for a very part-time SysAdmin.
- “Adam Jimerson: Introduction to PacBSD” happening at KnoxBUG on the 25th.
- PCEngines APU question.
- Installing Windows 10 Under the bhyve Hypervisor. (via)
- Lumina Desktop 1.1.0 released.
Remember I posted that LibreSSL is in base DragonFly, but not default? Well, it’s default now. You can have a system without OpenSSL at all, by rebuilding DragonFly-current and using up-to-date dports.
Update: see John’s comments for clarification: LibreSSL is default; the change is that OpenSSL isn’t even built any more. The result is still the same good news: you can have an OpenSSL-free DragonFly system now.
I don’t know how I ended up with 3 pfSense items to lead with – it just happened.
- pfsense 2.3.x passive ftp.
- PFsense DMZ on ESXi.
- Assistance with routing issue with pfSense VM.
- FreeNAS: Open Source Storage Operating System. (via)
- User manages to get OpenBSD and FreeBSD working with Libreboot. (via)
- HardenedBSD switches to LibreSSL in base as the default crypto lib. (via)
- BSD Question.
- Hardened Operating Systems.
- Performance Improvements for FreeBSD Kernel Debugging. (via)
- SNI support added to libtls, httpd in -current.
- Cover reveal for “PAM Mastery”.
- DiscoverBSD for 2016/08/22.
- Synth – A simple, fast drop-in alternative to 3Ps: Portmaster, Portupgrade, and Poudriere (for FreeBSD and DragonFly). Surely you knew of this already? (via)
There’s been multiple reports of pulseaudio causing problems for DragonFly users. It would get pulled in as a dependency, and audio would suddenly stop working. Uninstall, and audio is fine. John Marino has removed it from dports, to prevent that exact problem.
Because this always happens just after I create a DragonFly release, there’s a new version of OpenSSL. However, this is for version 1.0.2. 1.0.1 is what’s in the release, and it’s supported through the end of the year.
OpenSSH has a major version bump in DragonFly, to 7.3p1. This means some features – specifically patches for High Performance Networking – are no longer there, and you’ll get an error if your config file requires them. Either remove the options from your config, or install OpenSSH from dports.
If you happen to be testing kernel modules, DragonFly can now load them from a modules.local directory. This keeps modules that aren’t part of the base system, separate. This is probably of most use to developers. It’s controlled by local_modules being set in /boot/loader.conf, and defaults to on.
(Updated for correct file location – thanks, swildner)
I see this bite people irregularly over the years: if your default shell on login can’t run, what do you do? I’ve seen it happen because of a missing /usr/lib, and it can happen with out-of-date library references, too. There’s several different ways to deal with it:
- Run a shell that can’t have this problem, like /bin/tcsh (the root default).
- Or, rebuild in single-user mode from the console.
- Or, perform the bullet-proof upgrade.
That last one may be useful if your dports setup gets mangled, somehow – though ‘pkg upgrade’ has always worked for me.
For those of you running DragonFly-current, the already-mentioned library privatization going on means that ports have to be rebuilt. You will want to do it yourself, or wait a little bit before upgrading if you want to install binaries.
That’s a pretty cryptic headline, isn’t it? John Marino has ‘privatized’ several libraries in DragonFly, so that they can’t get included involuntarily as part of a port build. That may mean you will need to perform a full rebuild of your system if you are tracking DragonFly-current.
(This is the way to fix ‘system’ languages like Perl was in FreeBSD 4.x – keep them clearly separate from the port version. It’s about a decade too late for that idea to work out, though.)