From 45ccb1752ba71a70a578315034b844af51fc7ba2 Mon Sep 17 00:00:00 2001 From: "Timur I. Bakeyev" Date: Sun, 30 Jun 2019 23:09:37 +0000 Subject: Add two entries about upgradinf from previous versions of Samba to Samba 4.10. --- UPDATING | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 66 insertions(+), 1 deletion(-) (limited to 'UPDATING') diff --git a/UPDATING b/UPDATING index 55e63cd9c590..9edb20427e91 100644 --- a/UPDATING +++ b/UPDATING @@ -5,6 +5,71 @@ 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. + +20190630: + AFFECTS: users of net/samba410 + AUTHOR: timur@FreeBSD.org + + If you used Samba in AD/DC mode with the previous versions of the port on UFS2 + backed storage you have to add usage of vfs_freebsd VFS module for at least + SYSVOL share and confugure it to use 'legacy' mode(see manpage). + + The reason behind this is that previous versions Samba port used a hack to + workaround broken mapping of Linux security and trusted extended attributes + into FreeBSD namespace. In particular, essential security.NTACL attribute + was replaced with the user.NTACL and placed in a insecure USER namespace. + + This port dropped this hack in favor of vfs_freebsd module, which should + provide more controlled way of such a mapping. + + To maintain the compatibility with the previous installations on UFS2 storage + (as ZFS uses it's own way of mapping SYSVOL, thanks to the iXsystems patches) + the vfs_freebsd module provides 'legacy' mode that implements old functionality. + + For the presh installations it is recommended to use 'secure' mode of operations + for this module and use it as a global vfs objects. + + Caution: The given module is still considered EXPERIMENTAL. + +20190630: + AFFECTS: users of net/samba410, net/samba4[6-8] and devel/talloc?, devel/tevent?, + databases/tdb?, databases/ldb* + AUTHOR: timur@FreeBSD.org + + The port of the new version of Samba 4.10 is introduced. Due necessirity + to keep backwards compatibility for the legacy samba4[6-8] ports the + upgrade procedure is a bit convoluted. + + You are safe to perform fresh new install of samba410 port. In case you + are upgrading from the previous versions of Samba, please use the + following procedure: + + 0. Take backups of all the relevant files, in particular PREFIX/etc/smb4.conf + and /var/db/samba4/ subdirectory. Keep in mind that files there (may) + have extended attributes, so use appropriate tools to preserve them. + + 1a. If you haven't updated Samba between 20190619 and 20190630 then next + step should be as simple as: + + portmaster -o net/samba410 net/samba48 + + 1b. If you have been affected by the archiving legacy versions of + Samba-related libraries for legacy versions of Samba, which happened + in the given time frame, then you need to reverse operation from the + 20190619 entry: + + for users of portmaster: + portmaster -o devel/talloc devel/talloc1 + portmaster -o devel/tevent devel/tevent1 + portmaster -o databases/tdb databases/tdb1 + portmaster -o net/samba410 net/samba48 + + for users of portupgrade: + portupgrade -o devel/talloc devel/talloc1 + portupgrade -o devel/tevent devel/tevent1 + portupgrade -o databases/tdb databases/tdb1 + portupgrade -o net/samba410 net/samba48 + 20190619: AFFECTS: users of samba4[6-8] and devel/talloc, devel/tevent, databases/tdb, databases/ldb* AUTHOR: timur@FreeBSD.org @@ -22,7 +87,7 @@ you update your ports collection, before attempting any port upgrades. portmaster -o devel/talloc1 devel/talloc portmaster -o devel/tevent1 devel/tevent portmaster -o databases/tdb1 databases/tdb - portmaster -r devel/talloc1 + portmaster -r talloc1 for users of portupgrade: portupgrade -o devel/talloc1 devel/talloc -- cgit v1.2.3