You can obtain the samba source from the samba website. To obtain a development version, -you can download samba from CVS or using rsync.

31.1. Access Samba source code via CVS27.1. Access Samba source code via CVS

31.1.1. Introduction27.1.1. Introduction

Samba is developed in an open environment. Developers use CVS @@ -117,8 +193,8 @@ CLASS="SECT2" >

31.1.2. CVS Access to samba.org27.1.2. CVS Access to samba.org

The machine samba.org runs a publicly accessible CVS @@ -130,8 +206,8 @@ CLASS="SECT3" >

31.1.2.1. Access via CVSweb27.1.2.1. Access via CVSweb

You can access the source code via your @@ -151,8 +227,8 @@ CLASS="SECT3" >

31.1.2.2. Access via cvs27.1.2.2. Access via cvs

You can also access the source code via a @@ -256,8 +332,8 @@ CLASS="SECT1" >

31.2. Accessing the samba sources via rsync and ftp27.2. Accessing the samba sources via rsync and ftp

pserver.samba.org also exports unpacked copies of most parts of the CVS tree at

31.3. Building the Binaries27.3. Verifying Samba's PGP signature

In these days of insecurity, it's strongly recommended that you verify the PGP signature for any +source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of +all Samba downloads have had a corresponding PGP signature download (a very low percentage, which +should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP +signatures should be a standard reflex.

With that said, go ahead and download the following files:

     $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

The first file is the PGP signature for the Samba source file; the other is the Samba public +PGP key itself. Import the public PGP key with:

     $ gpg --import samba-pubkey.asc

And verify the Samba source code integrity with:

     $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc

If you receive a message like, "Good signature from Samba Distribution Verification Key..." +then all is well. The warnings about trust relationships can be ignored. An example of what +you would not want to see would be:

     gpg: BAD signature from "Samba Distribution Verification Key"

27.4. Building the Binaries

To do this, first run the program

31.3.1. Compiling samba with Active Directory support27.4.1. Compiling samba with Active Directory support

In order to compile samba with ADS support, you need to have installed @@ -393,9 +511,7 @@ BORDER="0" >

- -

If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.

31.3.1.1. Installing the required packages for Debian27.4.1.1. Installing the required packages for Debian

On Debian you need to install the following packages:

31.3.1.2. Installing the required packages for RedHat27.4.1.2. Installing the required packages for RedHat

On RedHat this means you should have at least:

31.4. Starting the smbd and nmbd27.5. Starting the smbd and nmbd

You must choose to start smbd and nmbd either @@ -533,8 +649,8 @@ CLASS="SECT2" >

31.4.1. Starting from inetd.conf27.5.1. Starting from inetd.conf

NOTE; The following will be different if @@ -711,8 +827,8 @@ CLASS="SECT2" >

31.4.2. Alternative: starting it as a daemon27.5.2. Alternative: starting it as a daemon

To start the server as a daemon you should create @@ -804,7 +920,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >Prev NextSamba and other CIFS clientsAppendixesReporting BugsMigration from NT4 PDC to Samba-3 PDC