DragonFly 4.6 released!

[Matthew Dillon]

Packages for the release users are good.  Both the new 4.6 release and the
older 4.4 release have been updated.

Packages for master... we blew it and the ABI was tagged wrong.  We are
throwing our big machine at the redo and will have updated packages for
master in-place tomorrow afternoon.  Master users can temporarily override
their ABI to use the 4.6 packages if need be by setting:

setenv ABI dragonfly:4.6:x86:64

If you can help it though, just wait until tomorrow if you use master and
want to upgrade your packages.  And don't accidently make any ABI override
you use permanent :-).

-Matt

On Tue, Aug 2, 2016 at 1:29 PM, Justin Sherrill <justin at shiningsilence.com>
wrote:

> DragonFly 4.6 is out!
>
> http://www.dragonflybsd.org/release46/
>
> > From the release page:
>
> "DragonFly version 4.6 brings more updates to accelerated video for
> both i915 and radeon users, home-grown support for NVMe controllers,
> preliminary EFI support, improvements in SMP and networking
> performance under heavy load, and a full range of binary packages."
>
> The release page has links to the tagging commits for this release,
> which have an exhaustive list of all the commits that went in since
> the last release.  The normal ISO and IMG files are available for
> download and install.
>
> If you have an existing 4.4.x system and are running a generic kernel,
> the normal upgrade process will work.  Change your local /usr/src to
> 4.6:
>
> > cd /usr/src
> > git fetch origin
> > git branch DragonFly_RELEASE_4_6 origin/DragonFly_RELEASE_4_6
> > git checkout DragonFly_RELEASE_4_6
> > git pull
>
> And then rebuild: (in /usr/src )
>
> > make buildworld
> > make buildkernel
> > make installkernel
> > make installworld
> > make upgrade
>
> Don't forget to upgrade your existing packages.  4.6 packages have
> already been built and are immediately available.
>
> > pkg upgrade
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160802/9e327582/attachment-0003.htm>