- WHATS NEW IN 1.9.17alpha4 - July 3rd 1997.
- ==========================================
+ WHATS NEW IN 1.9.17 - August 25th 1997
+ ======================================
+
+New stable release of Samba.
+----------------------------
+
+This is the new stable release of Samba, superceding
+the last stable release 1.9.16p11. All users are
+encouraged to upgrade to this new release as there have
+been many improvements to the code since that time.
+See the Frequently Asked Questions (under docs/faq) for
+an explanation of how the version numbering scheme works,
+distinguishing between stable and development releases.
+
+Changes since 1.9.16p11.
+------------------------
Improved browsing support.
--------------------------
as it has been largely re-written to explain how to do this.
*IMPORTANT* All Samba servers acting as local/domain master
-browsers must be running 1.9.17alpha3 (or later).
-
-Samba 1.9.17alpha4 should now keep global and authoritative
-browse lists separate - see docs/BROWSING.txt for full details.
+browsers must be running 1.9.17 (or later).
Thanks to Silicon Graphics for allowing us to test the new
code on their corporate network.
NetBench) correctly with many hundreds of concurrent PC's.
The confidence level on share mode handling in Samba
is now much higher than it was previously. PC database
-packages should be much safer when run against a
-Samba share. Thanks to Silicon Graphics for testing
-this code for us.
+packages should be safe when run against a Samba share.
+Thanks to Silicon Graphics for testing this code for us.
If at all possible compile Samba to use the new share
mode handling with shared memory (set the flags
IRIX 5.x.x
FreeBSD
-A crash bug with slow share modes in 1.9.17alpha3 has been
-corrected.
+Roving profile support.
+-----------------------
-Updated smb.conf documentation
-------------------------------
-All options are now documented we believe.
+Roving profiles are believed to work correctly
+with Windows NT 4.x and Windows 95. Domain logons
+are fully implemented *for Windows 95 machines only*.
+
+
+Updated documentation
+---------------------
+All options are now documented in the smb.conf man page
+we believe. Much work has been done by Samba Team members
+to improve the quality and quantity of the Samba documentation.
+
+A draft new structure for documentation is being worked on: see
+docs/faq/Samba-meta-FAQ for details. This will soon be a master
+reference to all Samba documentation.
Many bugfixes and improvements
------------------------------
From around the 'net around the world. Many
thanks to everyone who contributed.
-A list of the new code since alpha3 includes :
+Commercial thanks.
+------------------
-*** Fix for roaming profiles hanging on a Samba drive.
-*** smbclient can now query Win95/NT print queues.
-*** smbd can now rename across filesystem mount points.
-*** New 'force xxx mode' options allow more control over
- Unix file permissions.
-*** New 'client code page' option for internationalization
- support.
-*** Documentation update.
+Thanks to Cisco for the new netbios alias code support.
+Thanks to Silicon Graphics for the help with the cross
+subnet browsing and NetBench code.
+Thanks to Whistle for funding one of the Samba Team
+members.
-Remaining known issues with cross-subnet browsing.
---------------------------------------------------
-When nmbd is acting as a WINS server it doesn't handle
-de-registering of members of a WORKGROUP<1e> name correctly.
-The first machine to de-register will remove the name. This
-should be fixed in a later release when group names are
-handled correctly in the WINS code.
+Reporting bugs
+--------------
-Remember - this is new code so there may be
-bugs or problems.
-
-As always, all bugs are our responsibility -
-please report them to :
+The Samba Team believes that this is a stable
+production release, but all software has bugs.
+If you have problems, or think you have found a
+bug please email a report to :
samba-bugs@samba.anu.edu.au
+Stating the version number of Samba that you
+are running, and *full details* of the steps
+we need to reproduce the problem.
+
+As always, all bugs are our responsibility.
Regards,