DragonFly 4.2.3 released

There was a newer release of OpenSSL (1.0.1p) last week, so there’s a new revision of the DragonFly release – 4.2.3.  There’s little major change other than the security fix for OpenSSL.

Those readers who can count past 2 may notice that there wasn’t a 4.2.2.  We went straight from 4.2.1 to 4.2.3.   That’s my fault.  I screwed up tagging and Git doesn’t like repeated, deleted tags.

4 Replies to “DragonFly 4.2.3 released”

  1. Binary vs. source update question. Should a “pkg upgrade” apply the changes in 4.2.3 to a prior 4.2.x version?

  2. Todd – it will not, because pkg upgrade affects only ports. The base system is untouched. If you want to move to 4.2.3, you will need to download DragonFly src and rebuild. My strategy is:

    cd /usr
    make src-update
    cd src
    make buildworld
    make buildkernel
    make installkernel
    make installworld
    make upgrade

  3. Yes and that source update process runs very well nowadays, also when you have a powerful server, like with 16 cores and do it make -j 32 buildworld on it, it goes really fast.

Comments are closed.