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
Andrew Bartlett 47ece3f897 s3-param Make lp_piddir() const
This disables % substitutions in the 'pid dir' parameter.  This is
used all over the codebase, and need to be internally consistent
between all the Samba tasks.

Andrew Bartlett
2011-06-01 04:19:05 +02:00
auth build: Make auth_sam_reply a library 2011-05-18 16:12:08 +02:00
buildtools Add -fno-common where supported (WAF only) 2011-05-10 11:37:30 +09:30
codepages s4-charset: use dyn_CODEPAGEDIR for location of upcase.dat/lowcase.dat 2011-02-07 13:22:02 +11:00
docs-xml s3-param Make lp_passwordserver() const. 2011-06-01 04:19:05 +02:00
dynconfig dynconfig: Have only one dynconfig.o in the common code. 2011-04-27 22:22:26 +10:00
examples Remove the char * argument from the SMB_VFS_GETWD() call. Now always 2011-06-01 04:06:12 +02:00
include build: added placeholder files for public header directories 2011-03-15 12:22:18 +11:00
lib replace: remove waring if IOV_MAX is not defined 2011-05-31 18:36:53 +02:00
libcli Tiny simplification to dom_sid_string_buf 2011-05-31 23:16:31 +02:00
libds/common libds: moved enum security_types to a common header 2011-05-08 10:56:27 +02:00
libgpo Fix numerous missing dependencies in WAF build scripts 2011-05-25 19:22:13 +02:00
librpc librpc/ndr: Use converted_size to determine if NULL termination was sent 2011-06-01 01:42:21 +02:00
m4 m4: Don't AC_MSG_ERROR when too old python is found 2011-01-10 11:26:18 +01:00
nsswitch s3-lib Replace StrCaseCmp() with strcasecmp_m() 2011-05-18 16:12:08 +02:00
packaging packaging(RHEL-CTDB): align configure.rpm to the spec file 2011-05-27 13:27:02 +02:00
packaging4 Move README.Debian to the right directory. 2008-10-19 11:53:13 +02:00
pidl pidl: Add support for the [ignore] property 2011-04-05 23:46:04 +02:00
release-scripts release-scripts: add build-htmlman-nogit 2011-01-18 15:07:09 +01:00
script script/autobuild.py: don't force usage of ccache and gcc 2011-04-30 13:47:47 +02:00
selftest selftest: create ncalrpcdir with 0755 permissions 2011-05-23 13:26:33 +02:00
source3 s3-param Make lp_piddir() const 2011-06-01 04:19:05 +02:00
source4 librpc/ndr: add new LIBNDR_FLAG_STR_RAW8 for ndr_pull_string 2011-06-01 00:30:40 +02:00
swat rename swat => swat2, so that we don't conflict with samba3 2008-09-12 08:51:07 +02:00
testdata s4:setup/provision_rootdse_add.ldif - provide informations in the right order 2010-10-05 16:06:05 +00:00
testprogs s4: add blackbox test for rename 2011-05-21 09:50:34 +02:00
tests s3: Fix bug 7052: "DFS broken on AIX (maybe others)" 2010-01-21 14:21:26 +01:00
testsuite s3: Remove the smbtorture3 OPLOCK3 test 2011-05-22 21:07:40 +02:00
wintest wintest Allow setting of the firewall to fail 2011-04-07 14:35:36 +10:00
.bzrignore Add bzrignore symlink. 2010-12-18 00:47:06 +01:00
.gitignore s3-build: Move generated config.h and config.h.in to include/autoconf 2011-05-09 11:21:09 +02: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
MAINTAINERS.txt This reverts commit 378c4b221a. 2011-04-06 08:11:53 +02:00
Makefile waf: added top level build rules 2011-02-07 13:22:00 +11:00
Manifest s3: source/ is long gone :-) 2010-08-27 10:29:54 +02:00
merged-branches.txt prepare merging Samba3 and Samba4 together. 2008-09-11 16:01:26 +02:00
PFIF.txt
prog_guide4.txt s4:prog_guide4.txt: remove obsolete comments 2009-12-15 23:34:23 +01:00
Read-Manifest-Now
README README: Fix indentation of bullet point. 2009-06-03 16:26:29 +02:00
README.cifs-utils Update URL in README.cifs-utils 2010-04-02 06:26:09 -04:00
README.Coding README.Coding: fix typos 2010-07-10 14:15:08 +02:00
Roadmap 3.4 is released... 2009-07-17 22:40:24 +02:00
upgrading-samba4.txt Make upgrade procedure more explicit. 2010-09-29 04:23:07 +10:00
VERSION Fix alpha version - we're now working on alpha16. 2011-05-10 18:36:08 +02:00
WHATSNEW4.txt Remove reference to Samba4 LDAP backends 2011-05-03 07:37:06 +02:00
WHATSNEW.txt s3:WHATSNEW.txt: remove the "strict allocate" default value 2011-04-13 21:21:10 +02:00
wscript build: Remove --disable-s3build so we can rely on these subsystems 2011-05-09 12:25:33 +02:00
wscript_build build: Remove --disable-s3build so we can rely on these subsystems 2011-05-09 12:25:33 +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 NT 4.0 Domain Controller 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:

- smbfs, a 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.

- cifsvfs, a more 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.



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.

You could also send hardware/software/money/jewelry or pre-paid pizza
vouchers directly to Andrew. The pizza vouchers would be especially
welcome, in fact there is a special field in the survey for people who
have paid up their pizza :-)

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. However, as you can see from the user survey quite a lot of 
people do seem to like it at the moment :-)


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.


NEWS GROUP
----------

You might also like to look at the usenet news group comp.protocols.smb 
as it often contains lots of useful info and is frequented by lots of 
Samba users. The newsgroup was initially setup by people on the Samba 
mailing list. It is not, however, exclusive to Samba, it is a forum for 
discussing the SMB protocol (which Samba implements). The samba list 
is gatewayed to this newsgroup.


WEB SITE
--------

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

http://samba.org/samba/

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. Have you registered with the survey yet? :-)