X-Git-Url: https://gitweb.dragonflybsd.org/~nant/dragonfly.git/blobdiff_plain/fc46845363cf63e300f07e39332c23cf122c43d3..fa7cb8cead68200ada34caec5db4b217e3db696b:/UPDATING

diff --git a/UPDATING b/UPDATING
index ab9cb9f398..5a91da4f4a 100644
--- a/UPDATING
+++ b/UPDATING
@@ -7,8 +7,114 @@
 #
 # If you discover any problem, please contact the bugs@lists.dragonflybsd.org
 # mailing list with the details.
-#
-# $DragonFly: src/UPDATING,v 1.26 2008/09/15 20:03:36 thomas Exp $
+
++-----------------------------------------------------------------------+
++         UPGRADING DRAGONFLY FROM 2.10 to later versions               +
++-----------------------------------------------------------------------+
+
+SEVERAL ISA DRIVERS REMOVED
+---------------------------
+
+The following ISA only drivers have been removed along with a couple of
+associated userland tools:
+
+aha(4)
+asc(4) & sasc(1)
+ctx
+dgb(4)
+el(4)
+gpib
+gsc(4) & sgsc(1)
+ie(4)
+labpc(4)
+le(4)
+mse(4)
+rc(4)
+rdp(4)
+spigot
+tw(4) & xten(1) & xtend(8)
+wl(4) & wlconfig(8)
+wt(4)
+
+Note that two of these drivers (aha(4) and ie(4)) are in our GENERIC
+config and one (aha(4)) is in our X86_64_GENERIC kernel configuration
+file.
+
+If buildkernel complains about any of these drivers, just remove them
+from your kernel configuration.
+
++-----------------------------------------------------------------------+
++         UPGRADING DRAGONFLY FROM 2.8 to later versions                +
++-----------------------------------------------------------------------+
+
+GCC 4.4 & BINUTILS 2.21
+-----------------------
+
+GCC 4.4 has been made DragonFly's default compiler and Binutils 2.21 has
+been made DragonFly's default Binutils.
+
+That means that any settings that set CCVER to 'gcc44' are not needed
+anymore. Instead, CCVER can be set to 'gcc41' to go back to using
+GCC 4.1.
+
+It also means that 'binutils221' as a value for BINUTILSVER has no
+effect anymore. 2.17 has been removed and 'binutils220' is available
+as an option.
+
+The NO_GCC44 option has been removed and will not affect the build
+anymore. There is now a NO_GCC41 option that will prevent GCC 4.1 from
+building in a similar fashion.
+
+Note that you must do a full buildworld/buildkernel for upgrading.
+
+pkg_radd settings
+-----------------
+
+The config file for pkg_radd has moved from /etc/settings.conf to 
+/etc/pkg_radd.conf.  Save the contents of settings.conf before upgrading
+if this is needed.  This warning only applies if /etc/settings.conf 
+exists.  pkg_radd will continue to work with defaults.
+
++-----------------------------------------------------------------------+
++         20100927							+
++         UPGRADING DRAGONFLY FROM 2.6 to 2.8 or HEAD			+
++-----------------------------------------------------------------------+
+
+OpenSSL
+--------
+
+OpenSSL has been upgraded, and SHLIB_MAJOR was bumped for libssh and libcrypto.
+This shouldn't break any 3rd-party software, but you'll need to recompile your
+3rd-party software if you want it to link against the new version of OpenSSL.
+
+Loader
+-------
+
+A new loader (dloader) has been added which better handles booting from
+multiple kernel/module versions.
+
+To upgrade (Only for this upgrade, for post 2.8 upgrades see GENERAL below)
+
+	cd /usr/src
+	make buildworld
+	make installworld
+	make upgrade
+	make buildkernel KERNCONF=<KERNELNAME>
+	make installkernel KERNCONF=<KERNELNAME>
+
+Note that you must installworld and run the 'upgrade' target before
+installing the new kernel.
+
+BIND
+-----
+
+BIND has been removed from the base system.  The ldns and drill tools have 
+been added for basic functionality.  Use 'drill' where you would normally 
+use nslookup or dig, or install BIND from pkgsrc.  It's available as 
+net/bind95, net/bind96, or net/bind97 as of this writing.
+
+This only affects older systems upgrading to 2.8.  New 2.8+ installs 
+include BIND as a pkgsrc package.
 
 +-----------------------------------------------------------------------+
 +         UPGRADING DRAGONFLY ON AN EXISTING DRAGONFLY SYSTEM		+