1 WHATS NEW IN Samba 3.0 alphaX
2 =============================
6 - fixed nexus/win9x user list (jfm)
7 - fixed large user/group lists in winbindd (tridge)
8 - fixed gssapi headers in redhat (jmcd)
9 - fixed rap error code handling (jra)
10 - more usermanager rpc calls (jfm)
11 - re-added RAP calls at top level to net command (tridge)
15 - fixed a silly tdb bug in alpha2 that affected internal databases
19 - we no longer use cyrus-sasl for LDAP SASL/gssapi. This makes our ADS
20 code much more robust.
21 - winbindd cache code rewritten to be much more efficient. It also
22 copes much better with server outages.
23 - jfm implemented full group mapping and smb.conf option 'domain admin
24 group' is now gone. Consult the GROUP-MAPPING-HOWTO.txt to know how
25 to gain back administrator rights.
27 - numerous small bugfixes
31 - winbindd now uses LDAP and works correctly with an ADS server in
33 - XFS quotas code on Linux
34 - group mapping code from JFM
35 - "net rpc join" command replaces smbpasswd -j
36 - fixed winbind initgroups
40 This is a pre-release of Samba 3.0 alpha0. This is NOT a stable
41 release. Use at your own risk.
43 The purpose of this alpha release is to get wider testing of the major
44 new pieces of code in the current Samba 3.0 development tree. We are
45 planning on ceasing development on the 2.2.x release of Samba very
46 shortly and after that we will be concentrating on Samba 3.0. To
47 reduce the time before the final Samba 3.0 release we need as many
48 poeple as possible to start testing these alpha releases, and
49 hopefully giving us some high quality feedback on what needs fixing.
51 Note that Samba 3.0 is not anywhere near feature complete yet. There
52 is a lot more coding we have planned, but unless we get what we have
53 done already more widely tested we will have a hard time doing a
54 stable release in a reasonable time frame.
56 This release is also missing major pieces of documentation, and there
57 are many parts of the docs that have not been updated to reflect the
58 new options and features in 3.0.
63 - Active Directory support. This release is able to join a ADS realm
64 as a member server and authenticate users using
65 LDAP/kerberos. Please read ADS-HOWTO.txt in the release for a very
66 rough guide on how to set this up.
68 - Unicode support. Samba will now negotiate unicode on the wire and
69 interally there is now a much better infrastructure for multi-byte
70 and unicode character sets. You may need the "dos charset", "unix
71 charset" and "display charset" options. The unicode support is not
74 - New authentication system. The internal authentication system has
75 been almost completely rewritten. Most of the changes are internal,
76 but the new auth system is also very configurable. Not documented
79 - new filename mangling system. The filename mangling system has been
80 completely rewritten. An internal database now stores mangling maps
81 persistantly. This needs lots of testing.
83 - new "net" command. A new "net" command has been added. It is
84 somewhat similar to the "net" command in windows. Eventually we plan
85 to replace a bunch of other utilities (such as smbpasswd) with
86 subcommands in "net", at the moment only a few things are
89 - Samba now negotiates NT-style status32 codes on the wire. This
90 improves error handling a lot.
92 - better w2k printing support. The support for printing from win2000
93 clients has improved greatly.
95 Plus lots of other changes!
97 Note that many new features are not documented. Don't let this stop
98 you from using Samba 3.0. It is particularly important that the basic
99 file/print serving abilities of Samba 3.0 are widely tested to ensure
100 that we have not broken any of the basic functionality. As we do more
101 alpha releases we will start to document the new features.
104 Reporting bugs & Development Discussion
105 ---------------------------------------
107 Please discuss this release on the samba-technical mailing list or by
108 joining the #samba-technical IRC channel on irc.openprojects.net
110 If you do report problems then please try to send high quality
111 feedback. If you don't provide vital information to help us track down
112 the problem then you will probably be ignored.