Samba 3 is the current stable production version of Samba.
Samba 3 Features
- Stable, scalable File and Print server
- Windows NT and AD domain member
Samba 3 Roadmap
This is a compilation of things that we want to achieve in future versions of Samba 3. If you feel like developing for Samba, the best way to contact the developers on the #samba-technical irc channel on irc.freenode.net. Please note that this is really a developer channel, user questions will mainly be ignored there. But most active Samba developers are around according to their timezones.
- Easier configurability, more than 300 options in the smb.conf configuration file are way too many.
- Work has been started to do graphical wizards for example to join a domain.
- We would also appreciate someone taking care of swat. None of the core Samba developers is a good web developer, so swat is pretty much orphaned these days which is a pity.
- Internal restructuring to make contributions easier. We have come a long way in this respect since Samba 3.0 days, but we need to improve a lot.
- An important subproject of the internal restructuring is to make use of shared libraries. With Samba 3.2 we internally separated out libwbclient, libtalloc and libtdb and link them in as shared objects in all binaries. We will identify more such libraries and make them available to external projects.
- Re-work the RPC infrastructure. We will see external named pipe handlers, so that someone who wants to rewrite the SPOOLSS server does not have to understand or even link to the rest of smbd.
- Share technology with Samba 4. For example almost all RPC code in Samba 3.2 is converted to IDL using the PIDL compiler from Samba 4
- SMB2. This is quite a high priority for us, as sooner or later Vista will be our major client.
- Implement 100% of NTFS semantics as seen by clients:
- NTFS Alternate Data Streams support: This is done in Samba 3.2 with the streams_xattr and streams_depot modules, testing and ideas for different coding schemes for streams are welcome
- Windows-compatible ACLs: On  work has been started in this area, help is welcome.
- Encrypted File System: This is a completely new area, but now that the Microsoft protocol documentation is available via , it should be possible to implement.
- Make us scale better at the low end. This involves mainly reduced memory consumption. Samba 3.2 is an improvement here, but we would like to improve further here. One possible path is to adapt the Samba 4 single process model in Samba 3, but this requires a lot of internal code restructuring.
- Make us scale better at the hight end. Memory consumption is an important factor here as well, but equally important here is to make the Clustered_Samba better and easier to configure.
Compiling Samba 3
Samba has a number of build-time configuration options. These control options and features that can be useful in specific environments but might not be appropriate for all installations.