fsrvp: use fss server state storage back-end

[ddiss/samba.git] / WHATSNEW.txt

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index d623330f50e9eed8d4a739c0998827837e7952b8..30cc8860ecdd1c7aa5e577928d020108cb4365af 100644 (file)
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -401,6 +401,18 @@ For pure file server work, the binaries users would expect from that
 series (smbd, nmbd, winbindd, smbpasswd) continue to be available.
 
 
+Domain Member Support
+=====================
+
+Domain member support in the 'samba' binary is in its infancy, and
+is not comparable to the support found in 'winbindd'. As such, on
+Samba domain member servers, the binaries 'smbd', 'nmbd' and 'winbindd'
+are to be used, as known from Samba 3 domain member server setups.
+The only exceptions from this rule are the cases which explicitly
+require the 'samba' binary, namely running the ntvfs file server,
+the CIFS proxy or OpenChange on a domain member.
+
+
 DNS
 ===
 
@@ -450,11 +462,6 @@ Known Issues
   headers at compile time) is known to cause errors when dealing with
   non-ASCII characters.
 
-- Domain member support in the 'samba' binary is in its infancy, and
-  is not comparable to the support found in winbindd.  As such, do not
-  use the 'samba' binary (provided for the AD server) on a member
-  server.
-
 - There is no NetBIOS browsing support (network neighbourhood)
   available for the AD domain controller.  (Support in nmbd and smbd
   for classic domains and member/standalone servers is unchanged).