aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorBeech Rintoul <beech@FreeBSD.org>2008-01-18 21:46:50 +0000
committerBeech Rintoul <beech@FreeBSD.org>2008-01-18 21:46:50 +0000
commit116b51895d89be68b7e3255ab361378b52482324 (patch)
tree1a99d230030e4c1847801ba417d7a2f10c7ab4ce /UPDATING
parentbe461d32e39da872779da46270e585f59df9bb7c (diff)
downloadports-116b51895d89be68b7e3255ab361378b52482324.tar.gz
ports-116b51895d89be68b7e3255ab361378b52482324.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING40
1 files changed, 40 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index aa0c1ae60d32..ee471e5d0f7d 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,46 @@ You should get into the habit of checking this file for changes each
time you update your ports collection, before attempting any port
upgrades.
+20080118:
+ AFFECTS: users of net/freeradius
+ AUTHOR: David Wood <david@wood2.org.uk>
+
+ FreeRADIUS 2.0 is now available as the net/freeradius2 port. All
+ FreeRADIUS users are advised to consider upgrading to 2.0. It is the
+ FreeRADIUS team's intention to put the 1.x server into 'maintenance' mode with
+ just critical bug fixes.[1] 2.0 has many improvements including numerous bug
+ fixesthat were too difficult for the 1.x server, as well as many new features.
+
+ Before uninstalling 1.x, it is recommended that you backup your
+ configuration, which is typically in /usr/local/etc/raddb, then move
+ it out of the way. It is also worth backing up the default configuration,
+ which is typically in /usr/local/share/examples/freeradius/raddb.
+
+ 1.x configurations should work with the 2.0 server [2]. However the
+ port automatically upgrades any unedited files in the configuration when
+ you install a new version of FreeRADIUS. Installing 2.0 with the residue
+ of a 1.x configuration in the default location will result in a mixed 1.x and
+ 2.0 configuration that may not work.
+
+ The recommended approach is to diff your 1.x configuration against the
+ default 1.x configuration, then make corresponding changes to a copy
+ of the default 2.0 configuration. If you moved your 1.x configuration out of
+ the way before upgrading, you will have a 2.0 configuration ready to edit in
+ the default location. It is worth reading man 5 unlang for details of
+ the new FreeRADIUS 'un-language' before starting.
+
+ Alternatively, you can move your 1.x configuration to another
+ location, such as /usr/local/etc/raddb_v1, then edit /etc/rc.conf to point the
+ rc.d script to that location. For example:
+
+ radiusd_flags="-d /usr/local/etc/raddb_v1"
+
+ I cannot guarantee that all 1.x configurations will work with the 2.0
+ server,and I only recommend using a 1.x configuration as an interim measure.
+
+ [1] - http://www.freeradius.org/business/roadmap.html
+ [2] - http://preview.tinyurl.com/ysrr6a
+
20080114:
AFFECTS: users of devel/perforce
AUTHOR: lth@FreeBSD.org