1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
https://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub)
Go to file
Rusty Russell 7c1d9fb3c1 ntdb: take advantage of direct access across expand.
This means we no longer have to unmap if we want to compare a record.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2012-06-22 07:35:17 +02:00
auth auth-kerberos: avoid crash with MIT krb5 1.10.0 in gss_get_name_attribute() 2012-06-06 18:22:51 +02:00
buildtools wafsamba/irixcc: next try to inject '-c99' the the build 2012-06-20 12:58:57 +02:00
codepages s4-charset: use dyn_CODEPAGEDIR for location of upcase.dat/lowcase.dat 2011-02-07 13:22:02 +11:00
ctdb/include Add current headers from ctdb master. 2012-06-21 23:49:19 +02:00
dfs_server lib/param: Create a seperate server role for "active directory domain controller" 2012-06-15 09:18:33 +02:00
docs-xml docs-xml: vfs_gpfs: add comment "per share option" 2012-06-15 18:32:23 +02:00
dynconfig dynconfig/wscript: correctly cleanup PRIVATELIBDIR and MODULESDIR defaults 2012-01-19 00:47:49 +01:00
examples examples/VFS: don't use smbd/proto.h 2012-06-06 10:18:38 +02:00
file_server s3-auth: rework default auth methods around the lp_server_role() parameter 2012-06-15 09:18:33 +02:00
include build: added placeholder files for public header directories 2011-03-15 12:22:18 +11:00
lib ntdb: take advantage of direct access across expand. 2012-06-22 07:35:17 +02:00
libcli Fix warning: variable ‘XX’ set but not used. 2012-06-19 10:27:23 -07:00
libds/common lib/param: Create a seperate server role for "active directory domain controller" 2012-06-15 09:18:33 +02:00
libgpo s3: fix build without ads support 2012-06-13 21:20:15 +02:00
librpc auth: Use only security_token_is_system to determine that a user is SYSTEM 2012-06-19 10:38:13 +02:00
m4 m4: Don't AC_MSG_ERROR when too old python is found 2011-01-10 11:26:18 +01:00
nsswitch nsstest: fix use of a non-existent word (existant) 2012-06-12 07:21:41 +02:00
packaging systemd: Add samba service file. 2012-04-04 18:04:09 +02:00
pidl pidl/tests: fix use of a non-existent word (existant) 2012-06-12 07:21:41 +02:00
release-scripts release-scripts/create-tarball: always create a tag in form of samba-${version} 2011-06-30 17:12:05 +02:00
script autobuild: always set TDB_NO_FSYNC. 2012-06-22 07:35:16 +02:00
selftest s4:torture/smb2: add smb2.durable-open.lock-oplock 2012-06-22 03:37:54 +02:00
source3 Fix bug #8974 - Kernel oplocks are broken when uid(file) != uid(process). 2012-06-21 21:53:58 +02:00
source4 s4:torture/smb2: add smb2.durable-open.lock-oplock 2012-06-22 03:37:54 +02:00
swat s3-docs: Remove references to long-gone smbmount utilities 2012-02-08 17:34:53 +11:00
testdata s4-s3upgrade: Add my wins.dat and fix the parsing error 2012-06-16 08:18:10 +02:00
testprogs s4-selftest: Add tests for dbcheck on an old database that needs repair 2012-06-16 05:44:15 +02:00
tests build: Fix bitrotted configure summary, we now also test HAVE_IFACE_GETIFADDRS 2012-04-05 02:39:09 +02:00
testsuite ntdb: put it back into the build. 2012-06-19 05:38:07 +02:00
utils libcli/dns: make 'clidns' private library out of DNS code in WAF build 2012-05-23 17:51:50 +03:00
wintest wintest: enable dns forwarding for internal dns 2012-06-21 23:47:35 +02:00
.bzrignore Add bzrignore symlink. 2010-12-18 00:47:06 +01:00
.gitignore s3-build: Do not write loadparm generated files into the build tree 2012-06-15 11:10:14 +02:00
.testr.conf testr: Use test lists. 2011-11-30 22:58:04 +01:00
BUILD_SYSTEMS.txt doc: Explain our build systems for Samba 4.0 2012-05-25 10:17:50 +10:00
callcatcher-exceptions.grep build: Add exceptions for callcatcher unused function detection 2012-02-17 09:12:47 +01:00
configure waf: added top level build rules 2011-02-07 13:22:00 +11:00
configure.developer build: added configure.developer for top level build 2011-02-07 13:22:01 +11:00
COPYING
howto4.txt s4: point to the wiki howto for s4 2010-11-09 23:38:28 +00:00
install_with_python.sh build: Add a script to install python and Samba with one command 2011-06-23 14:56:54 +02:00
MAINTAINERS.txt Add myself as libcli/dns maintainer 2012-05-30 00:38:00 +02:00
Makefile Add 'make pep8' target. 2011-12-09 00:25:13 +01:00
merged-branches.txt
PFIF.txt
prog_guide4.txt s4:prog_guide4.txt: remove obsolete comments 2009-12-15 23:34:23 +01:00
README Remove outdated information from the README 2011-12-07 03:09:08 +01:00
README.cifs-utils Update URL in README.cifs-utils 2010-04-02 06:26:09 -04:00
README.Coding CodingStyle: Add some notes about Python 2.4 compatibility. 2011-10-14 00:22:57 +02:00
README.contributing Add new contributing FAQ announcing acceptance of corporate (C). 2011-10-12 03:46:41 +02:00
README.packaging4 remove the fedora package, and point at the repository instead 2011-07-23 22:08:09 +02:00
Roadmap Roadmap: Clarify that 4.0 is our next release 2012-06-05 09:48:05 +02:00
upgrading-samba4.txt upgradedns: Rename to less generic name samba_upgradedns. 2012-02-24 15:07:25 +01:00
VERSION VERSION: Move on to beta3! 2012-06-20 10:14:36 +02:00
WHATSNEW.txt WHATNEW: Update for the beta2 release 2012-06-20 16:22:41 +10:00
wscript Add --disable-ntdb option for building. 2012-06-21 19:59:57 +02:00
wscript_build Add --disable-ntdb option for building. 2012-06-21 19:59:57 +02:00
wscript_build_embedded_heimdal waf: move krb5 checks to a separate waf file 2012-04-23 16:38:43 -04:00
wscript_build_system_heimdal waf: move krb5 checks to a separate waf file 2012-04-23 16:38:43 -04:00
wscript_build_system_mitkrb5 waf: Use Logs.info() instead of print. 2012-04-17 17:48:23 +02:00
wscript_configure_system_mitkrb5 waf: fix parsing krb5-config --version for MIT krb5 2012-06-07 17:03:01 +02:00

This is the release version of Samba, the free SMB and CIFS client and
server 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 in 
      docs/htmldocs/Samba3-HOWTO/install.html

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). 


WHAT IS SMB/CIFS?
=================

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 http://samba.org/cifs.


WHY DO PEOPLE WANT TO USE SMB?
==============================

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 
   clients.

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


WHAT CAN SAMBA DO?
==================

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
http://samba.org/samba, 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.



CONTRIBUTIONS
=============

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 http://samba.org/samba/devel/ 
for more details) and are always glad to receive feedback or 
suggestions to the address samba@lists.samba.org.  More information
on the various Samba mailing lists can be found at http://lists.samba.org/.

You can also get the Samba sourcecode straight from the git repository - see
http://wiki.samba.org/index.php/Using_Git_for_Samba_Development.

If you like a particular feature then look through the git change-log
(on the web at http://gitweb.samba.org/?p=samba.git;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.

MORE INFO
=========

DOCUMENTATION
-------------

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 samba@samba.org mailing list.  See the next section for details 
on subscribing to samba mailing lists.


MAILING LIST
------------

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

There is a mailing list for discussion of Samba.  For details go to
<http://lists.samba.org/> or send mail to <samba-subscribe@lists.samba.org>

There is also an announcement mailing list where new versions are
announced.  To subscribe go to <http://lists.samba.org/> or send mail
to <samba-announce-subscribe@lists.samba.org>.  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
<http://lists.samba.org/>


MAILING LIST ETIQUETTE
----------------------

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. groups.google.com.


WEB SITE
--------

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

http://samba.org/

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.