This project is a fork of the Samba.git project. If you have that one already cloned locally, you can use
git clone --reference /path/to/your/Samba.git/incarnation mirror_URL
to save bandwidth during cloning.
last changeMon, 25 Mar 2013 18:42:30 +0000 (25 19:42 +0100)
content tags
This is the release version of Samba, the free SMB and CIFS client and
server and Domain Controller for UNIX and other operating
systems. Samba is maintained by the Samba Team, who support the
original author, Andrew Tridgell.

>>>> Please read THE WHOLE of this file as it gives important information
>>>> about the configuration and use of Samba.

NOTE: Installation instructions may be found
      for the file/print server and domain member in:

      For the AD DC implementation a full HOWTO is provided at:

This software is freely distributable under the GNU public license, a
copy of which you should have received with this software (in a file
called COPYING). 


This is a big question. 

The very short answer is that it is the protocol by which a lot of
PC-related machines share files and printers and other information
such as lists of available files and printers. Operating systems that
support this natively include Windows 9x, Windows NT (and derivatives), 
OS/2, Mac OS X and Linux.  Add on packages that achieve the same 
thing are available for DOS, Windows 3.1, VMS, Unix of all kinds, 
MVS, and more.  Some Web Browsers can speak this protocol as well 
(smb://).  Alternatives to SMB include Netware, NFS, Appletalk, 
Banyan Vines, Decnet etc; many of these have advantages but none are 
both public specifications and widely implemented in desktop machines 
by default.

The Common Internet File system (CIFS) is what the new SMB initiative
is called. For details watch


1. Many people want to integrate their Microsoft desktop clients
   with their Unix servers.

2. Others want to integrate their Microsoft (etc) servers with Unix
   servers. This is a different problem to integrating desktop 

3. Others want to replace protocols like NFS, DecNet and Novell NCP,
   especially when used with PCs.


Please refer to the WHATSNEW.txt included with this README for
a list of features in the latest Samba release.

Here is a very short list of what samba includes, and what it does. 
For many networks this can be simply summarized by "Samba provides 
a complete replacement for Windows NT, Warp, NFS or Netware servers."

- a SMB server, to provide Windows NT and LAN Manager-style file and print 
  services to SMB clients such as Windows 95, Warp Server, smbfs and others.

- a Windows Domain Controller (NT4 and AD) replacement.

- a file/print server that can act as a member of a Windows NT 4.0
  or Active Directory domain.

- a NetBIOS (rfc1001/1002) nameserver, which amongst other things gives 
  browsing support. Samba can be the master browser on your LAN if you wish.

- a ftp-like SMB client so you can access PC resources (disks and
  printers) from UNIX, Netware, and other operating systems

- a tar extension to the client for backing up PCs

- limited command-line tool that supports some of the NT administrative
  functionality, which can be used on Samba, NT workstation and NT server.

For a much better overview have a look at the web site at, and browse the user survey.

Related packages include:

- cifsvfs, an advanced Linux-only filesystem allowing you to mount 
  remote SMB filesystems from PCs on your Linux box. This is included 
  as standard with Linux 2.5 and later.

- smbfs, the previous Linux-only filesystem allowing you to mount remote SMB
  filesystems from PCs on your Linux box. This is included as standard with
  Linux 2.0 and later.


If you want to contribute to the development of the software then
please join the mailing list. The Samba team accepts patches
(preferably in "diff -u" format, see 
for more details) and are always glad to receive feedback or 
suggestions to the address  More information
on the various Samba mailing lists can be found at

You can also get the Samba sourcecode straight from the git repository - see

If you like a particular feature then look through the git change-log
(on the web at;a=summary) and see
who added it, then send them an email.

Remember that free software of this kind lives or dies by the response
we get. If no one tells us they like it then we'll probably move onto
something else.



There is quite a bit of documentation included with the package,
including man pages, and lots of .html files with hints and useful
info. This is also available from the web page. There is a growing
collection of information under docs/.

A list of Samba documentation in languages other than English is
available on the web page.

If you would like to help with the documentation, please coodinate 
on the mailing list.  See the next section for details 
on subscribing to samba mailing lists.


Please do NOT send subscription/unsubscription requests to the lists!

There is a mailing list for discussion of Samba.  For details go to
<> or send mail to <>

There is also an announcement mailing list where new versions are
announced.  To subscribe go to <> or send mail
to <>.  All announcements also
go to the samba list, so you only need to be on one.

For details of other Samba mailing lists and for access to archives, see


A few tips when submitting to this or any mailing list.

1. Make your subject short and descriptive. Avoid the words "help" or
   "Samba" in the subject. The readers of this list already know that
   a) you need help, and b) you are writing about samba (of course,
   you may need to distinguish between Samba PDC and other file
   sharing software). Avoid phrases such as "what is" and "how do
   i". Some good subject lines might look like "Slow response with
   Excel files" or "Migrating from Samba PDC to NT PDC".

2. If you include the original message in your reply, trim it so that
   only the relevant lines, enough to establish context, are
   included. Chances are (since this is a mailing list) we've already
   read the original message.

3. Trim irrelevant headers from the original message in your
   reply. All we need to see is a) From, b) Date, and c) Subject. We
   don't even really need the Subject, if you haven't changed
   it. Better yet is to just preface the original message with "On
   [date] [someone] wrote:".

4. Please don't reply to or argue about spam, spam filters or viruses
   on any Samba lists. We do have a spam filtering system that is
   working quite well thank you very much but occasionally unwanted
   messages slip through. Deal with it.

5. Never say "Me too." It doesn't help anyone solve the
   problem. Instead, if you ARE having the same problem, give more
   information. Have you seen something that the other writer hasn't
   mentioned, which may be helpful?

6. If you ask about a problem, then come up with the solution on your
   own or through another source, by all means post it. Someone else
   may have the same problem and is waiting for an answer, but never
   hears of it.

7. Give as much *relevant* information as possible such as Samba
   release number, OS, kernel version, etc...

8. RTFM. Google.


A Samba WWW site has been setup with lots of useful info. Connect to:

As well as general information and documentation, this also has searchable 
archives of the mailing list and a user survey that shows who else is using
this package.
2013-03-25 Volker Lendeckedbwrap: Use tdb_null in db_ctdb_deletemaster
2013-03-25 Andrew Bartlettscripting: Fill the ProvisionNames hash with strings...
2013-03-25 Andrew Bartlettsamba-tool ldapcmp: Remove the GUID -> name mappings
2013-03-25 Andrew Bartlettselftest: Add tests for samba-tool dbcheck --reset...
2013-03-25 Andrew Bartlettscripting: Modify samba.descriptor.get_diff_sds() to...
2013-03-25 Andrew Bartlettsamba-tool dbcheck: Allow dbcheck to correct an nTSecur...
2013-03-25 Andrew Bartlettsamba-tool dbcheck: Add --reset-well-known-acls
2013-03-25 Andrew Bartlettscripting: Move get_diff_sds from samba.upgradehelpers...
2013-03-25 Andrew Bartlettscripting: Modify samba.descriptor.get_wellknown_sds...
2013-03-25 Andrew Bartlettscripting: Move samba.provision.descriptor to samba...
2013-03-25 Andrew Bartlettscripting: Make samba.provision.descriptor.get_wellknow...
2013-03-25 Andrew Bartlettscripting: Fix documentation comment on upgradehelpers...
2013-03-25 Andrew Bartlettscripting: Move the list of well known SDs to samba...
2013-03-25 Andrew Bartlettbuild: Do not pass CPP="" to pidl, skip the env variabl...
2013-03-25 Andrew Bartlettbuild: Remove the forced use of only the first part...
2013-03-24 Andrew Bartlettvfs-btrfs: Fix build on 32 bit platforms by using long...
4 years ago release-3-5-9 tag release-3-5-9
4 years ago release-3-6-0rc2 tag release-3-6-0rc2
4 years ago release-3-6-0rc1 tag release-3-6-0rc1
4 years ago release-3-6-0pre3 tag release-3-6-0pre3
4 years ago release-4-0-0alpha15 Release alpha15.
4 years ago ldb-1-1-0 ldb: tag release ldb-1-1-0
4 years ago release-3-4-13 tag release-3-4-13
4 years ago release-3-6-0pre2 tag release-3-6-0pre2
4 years ago tevent-0-9-11 tevent: tag release tevent-0-9-11
4 years ago release-3-5-8 tag release-3-5-8
4 years ago release-3-3-15 tag release-3-3-15
4 years ago release-3-4-12 tag release-3-4-12
4 years ago release-3-5-7 tag release-3-5-7
4 years ago release-3-4-11 tag release-3-4-11
4 years ago release-3-4-10 tag release-3-4-10
4 years ago release-4-0-0alpha14 Tag 4.0.0alpha14.
19 months ago wip/witness
19 months ago wip/dcerpc
20 months ago wip/durable
21 months ago wip/sec_vt
23 months ago netapp
2 years ago wip/dcerpc-1
2 years ago wip/cleanup
2 years ago wip/cleanup-20130709
2 years ago wip/cleanup-20130524
2 years ago testenv
2 years ago am_parent
2 years ago wip/cleanup-20130418
2 years ago wip/scavenger
2 years ago wip/cleanup-20130415
2 years ago wip/cleanup-20130410
2 years ago wip/scavenger-20130408