aboutsummaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authortdb <tdb@FreeBSD.org>2011-06-05 20:46:30 +0800
committertdb <tdb@FreeBSD.org>2011-06-05 20:46:30 +0800
commitd74512bc9203cc819df391bad8b83960703be4bd (patch)
treec42cfa6921c8ea3823eeeb23c344b8f9c3e3dcf7 /UPDATING
parent7b6911ddaac90e9816947bc83fa12510512c3e19 (diff)
downloadfreebsd-ports-gnome-d74512bc9203cc819df391bad8b83960703be4bd.tar.gz
freebsd-ports-gnome-d74512bc9203cc819df391bad8b83960703be4bd.tar.zst
freebsd-ports-gnome-d74512bc9203cc819df391bad8b83960703be4bd.zip
- Update zfSnap to 1.10.0
This includes a workaround for use with zpool v28. See UPDATING for more information. PR: ports/157621 Submitted by: Aldis Berjoza <aldis@bsdroot.lv> (maintainer)
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING13
1 files changed, 13 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 3a1a923ac228..479e01b89ce3 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,19 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20110605:
+ AFFECTS: users of sysutils/zfsnap
+ AUTHOR: Aldis Berjoza <aldis@bsdroot.lv>
+
+ There is an issue with zpool v28 (currently only on 9-CURRENT, or
+ 8-STABLE systems that have been manually patched) that affects
+ zfSnap. If you are using v28 make sure to use the -zpool28fix flag
+ with zfsnap to work around the problem.
+
+ For more information please see:
+
+ http://wiki.bsdroot.lv/zfsnap#zpool_v28_zfs_destroy_-r_bug
+
20110602:
AFFECTS: users of net/freeradius
AUTHOR: Sevan Janiyan <venture37@geeklan.co.uk>