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