From ad0e01e75059bedde6400529f1a5193ef9735e9b Mon Sep 17 00:00:00 2001
From: Gerald Carter All about Samba - what it is, how to get it, related sources of
-information, how to understand the numbering scheme, pizza
-details. Samba is a suite of programs which work together to allow clients to
-access to a server's filespace and printers via the SMB (Server Message
-Block) and CIFS (Common Internet Filesystem) protocols. Initially
-written for Unix, Samba now also runs on Netware, OS/2, VMS, StratOS and
-Amigas. Ports to BeOS and other operating systems are underway. Samba
-gives the capability for these operating systems to behave much like a
-LAN Server, Windows NT Server or Pathworks machine, only with added
-functionality and flexibility designed to make life easier for
-administrators. This means that using Samba you can share a server's disks and printers
-to many sorts of network clients, including Lan Manager, Windows for
-Workgroups, Windows NT, Linux, OS/2, and AIX. There is also a generic
-client program supplied as part of the Samba suite which gives a user on
-the server an ftp-like interface to access filespace and printers on any
-other SMB/CIFS servers. SMB has been implemented over many protocols, including XNS, NBT, IPX,
-NetBEUI and TCP/IP. Samba only uses TCP/IP. This is not likely to change
-although there have been some requests for NetBEUI support. Many users report that compared to other SMB implementations Samba is
-more stable, faster, and compatible with more clients. Administrators of
-some large installations say that Samba is the only SMB server available
-which will scale to many tens of thousands of users without crashing.
-The easy way to test these claims is to download it and try it for
-yourself! The suite is supplied with full source code under the
-GNU Public License. The GPL means that you can
-use Samba for whatever purpose you wish (including changing the source
-or selling it for money) but under all circumstances the source code
-must be made freely available. A copy of the GPL must always be included
-in any copy of the package. The primary creator of the Samba suite is Andrew Tridgell. Later
-versions incorporate much effort by many net.helpers. The man pages
-and this FAQ were originally written by Karl Auer. At time of writing, the current version was 1.9.17. If you want to be
-sure check the bottom of the change-log file.
-ftp://samba.org/pub/samba/alpha/change-log For more information see
-What do the version numbers mean? The Samba suite is available via anonymous ftp from samba.org and
-many
-mirror sites. You will get much
-faster performance if you use a mirror site. The latest and greatest
-versions of the suite are in the directory: /pub/samba/ Development (read "alpha") versions, which are NOT necessarily stable
-and which do NOT necessarily have accurate documentation, are available
-in the directory: /pub/samba/alpha Note that binaries are NOT included in any of the above. Samba is
-distributed ONLY in source form, though binaries may be available from
-other sites. Most Linux distributions, for example, do contain Samba
-binaries for that platform. The VMS, OS/2, Netware and Amiga and other
-ports typically have binaries made available. A special case is vendor-provided binary packages. Samba binaries and
-default configuration files are put into packages for a specific
-operating system. RedHat Linux and Sun Solaris (Sparc and x86) is
-already included, and others such as OS/2 may follow. All packages are
-in the directory: /pub/samba/Binary_Packages/"OS_Vendor" It is not recommended that you run a version of Samba with the word
-"alpha" in its name unless you know what you are doing and are willing
-to do some debugging. Many, many people just get the latest
-recommended stable release version and are happy. If you are brave, by
-all means take the plunge and help with the testing and development -
-but don't install it on your departmental server. Samba is typically
-very stable and safe, and this is mostly due to the policy of many
-public releases. How the scheme works:
-
-2. General Information
-
-
-2.1 What is Samba?
-
-
-2.2 What is the current version of Samba?
-
-
-2.3 Where can I get it?
-
-
-2.4 What do the version numbers mean?
-
-
-
-
-
So the progression goes:
--
- 1.9.16p10 (production) - 1.9.16p11 (production) - 1.9.17alpha1 (test sites only) - : - 1.9.17alpha20 (test sites only) - 1.9.17 (production) - 1.9.17p1 (production) -- -
The above system means that whenever someone looks at the samba ftp -site they will be able to grab the highest numbered release without an -alpha in the name and be sure of getting the current recommended -version.
- - -There are a number of places to look for more information on Samba, -including:
--
Send email to -listproc@samba.org. Make sure the subject line is blank, -and include the following two lines in the body of the message:
--
-
-subscribe samba Firstname Lastname
-subscribe samba-announce Firstname Lastname
-
-
-
-Obviously you should substitute YOUR first name for "Firstname" and -YOUR last name for "Lastname"! Try not to send any signature, it -sometimes confuses the list processor.
-The samba list is a digest list - every eight hours or so it sends a -single message containing all the messages that have been received by -the list since the last time and sends a copy of this message to all -subscribers. There are thousands of people on this list.
-If you stop being interested in Samba, please send another email to -listproc@samba.org. Make sure the subject line is blank, and -include the following two lines in the body of the message:
--
-
-unsubscribe samba
-unsubscribe samba-announce
-
-
-
-The From: line in your message MUST be the same -address you used when you subscribed.
- - -DO NOT post messages on mailing lists or in newsgroups until you have -carried out the first three steps given here!
--
If you still haven't got anywhere, ask the mailing list or newsgroup. In -general nobody minds answering questions provided you have followed the -preceding steps. It might be a good idea to scan the archives of the -mailing list, which are available through the Samba web site described -in the previous section. When you post be sure to include a good -description of your environment and your problem.
-If you successfully solve a problem, please mail the FAQ maintainer a -succinct description of the symptom, the problem and the solution, so -that an explanation can be incorporated into the next version.
- - -If you make changes to the source code, please submit these patches -so that everyone else gets the benefit of your work. This is one of -the most important aspects to the maintainence of Samba. Send all -patches to -samba@samba.org. Do not send patches to Andrew Tridgell or any -other individual, they may be lost if you do.
-Patch format -------------
-If you are sending a patch to fix a problem then please don't just use -standard diff format. As an example, samba@samba.org received this patch from -someone:
-382a -#endif -.. -381a -#if !defined(NEWS61)
-How are we supposed to work out what this does and where it goes? These -sort of patches only work if we both have identical files in the first -place. The Samba sources are constantly changing at the hands of multiple -developers, so it doesn't work.
-Please use either context diffs or (even better) unified diffs. You -get these using "diff -c4" or "diff -u". If you don't have a diff that -can generate these then please send manualy commented patches to I -know what is being changed and where. Most patches are applied by hand so -the info must be clear.
-This is a basic guideline that will assist us with assessing your problem -more efficiently :
-Machine Arch: -Machine OS: -OS Version: -Kernel:
-Compiler: -Libc Version:
-Samba Version:
-Network Layout (description):
-What else is on machine (services, etc):
-Some extras :
--
If you have spotted something very serious and believe that it is -important to contact the developers quickly send a message to -samba-urgent@samba.org. This will be processed more quickly than -mail to samba@samba.org. Please think carefully before using this address. An -example of its use might be to report a security hole.
-Examples of things not to send to samba-urgent include problems -getting Samba to work at all and bugs that cannot potentially cause damage.
- - -Samba has a large network of consultants who provide Samba support on a -commercial basis. The list is included in the package in -../Support.txt, and the latest version will always be on the main -samba ftp site. Any company in the world can request that the samba team -include their details in Support.txt so we can give no guarantee of -their services.
- - -- - -Those who have registered in the Samba survey as "Pizza Factory" will -already know this, but the rest may need some help. Andrew doesn't ask -for payment, but he does appreciate it when people give him -pizza. This calls for a little organisation when the pizza donor is -twenty thousand kilometres away, but it has been done.
--