Near-term dports work

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.

In Other BSDs for 2016/10/22

Oddball links for BSD this week – but pay attention to the first one.

LibreSSL not just available but default

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.

In Other BSDs for 2016/08/27

I don’t know how I ended up with 3 pfSense items to lead with – it just happened.

 

OpenSSH, OpenSSL updates

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.

Default shells and library changes

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:

That last one may be useful if your dports setup gets mangled, somehow – though ‘pkg upgrade’ has always worked for me.