Chapter 36. How to compile SAMBA

Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as "commit") new source code. Samba's various CVS branches can @@ -12,12 +11,12 @@ detailed in this chapter.

This chapter is a modified version of the instructions found at http://samba.org/samba/cvs.html -

CVS Access to samba.org

The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, including samba, rsync, distcc, ccache and jitterbug. There are two main ways of accessing the CVS server on this host. -

Access via CVSweb

You can access the source code via your favourite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision @@ -25,7 +24,7 @@ history and commit logs of individual files. You can also ask for a diff listing between any two versions on the repository.

Use the URL : http://samba.org/cgi-bin/cvsweb -

Access via cvs

You can also access the source code via a normal cvs client. This gives you much more control over what you can do with the repository and allows you to checkout whole source trees @@ -67,7 +66,7 @@ on this system just substitute the correct package name -r and defining a tag name. A list of branch tag names can be found on the "Development" page of the samba web site. A common request is to obtain the latest 3.0 release code. This could be done by - using the following userinput. + using the following command:

cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_3_0 samba

@@ -75,7 +74,7 @@ on this system just substitute the correct package name the following command from within the samba directory:

cvs update -d -P -

Accessing the samba sources via rsync and ftp

pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. @@ -84,7 +83,7 @@ on this system just substitute the correct package name The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. -

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. Even if you're not downloading from a mirror site, verifying PGP signatures should be a @@ -111,7 +110,7 @@ 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" -

Building the Binaries

To do this, first run the program ./configure +

Building the Binaries

To do this, first run the program ./configure in the source directory. This should automatically configure Samba for your operating system. If you have unusual needs then you may wish to run

root# ./configure --help @@ -124,10 +123,10 @@ example of what you would not want to see would be: of Samba you might like to know that the old versions of the binaries will be renamed with a ".old" extension. You can go back to the previous version with

root# make revert -

if you find this version a disaster!

`Compiling samba with Active Directory support`

In order to compile samba with ADS support, you need to have installed +

if you find this version a disaster!

Compiling samba with Active Directory support

In order to compile samba with ADS support, you need to have installed on your system:

the MIT kerberos development libraries (either install from the sources or use a package). The - heimdal libraries will not work.
the OpenLDAP development libraries.

If your kerberos libraries are in a non-standard location then + Heimdal libraries will not work.

the OpenLDAP development libraries.

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

After you run configure make sure that include/config.h it generates contains lines like @@ -136,13 +135,13 @@ example of what you would not want to see would be: #define HAVE_LDAP 1

If it doesn't then configure did not find your krb5 libraries or your ldap libraries. Look in config.log to figure - out why and fix it.

Installing the required packages for Debian

On Debian you need to install the following packages:

-
libkrb5-dev
krb5-user
-

Installing the required packages for RedHat

On RedHat this means you should have at least:

-
krb5-workstation (for kinit)
krb5-libs (for linking with)
krb5-devel (because you are compiling from source)
-
in addition to the standard development environment.
Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

Starting the smbd and nmbd

You must choose to start smbd and nmbd either - as daemons or from inetdDon't try + out why and fix it.

Installing the required packages for Debian

On Debian you need to install the following packages:

libkrb5-dev

krb5-user

Installing the required packages for RedHat

On RedHat this means you should have at least:

krb5-workstation (for kinit)

krb5-libs (for linking with)

krb5-devel (because you are compiling from source)

in addition to the standard development environment.

Note that these are not standard on a RedHat install, and you may need + to get them off CD2.

Starting the smbd and nmbd

You must choose to start smbd and nmbd either + as daemons or from inetd. Don't try to do both! Either you can put them in inetd.conf and have them started on demand by inetd, or you can start them as @@ -153,7 +152,7 @@ example of what you would not want to see would be: Samba. In many cases you must be root.

The main advantage of starting smbd and nmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection - request.

Starting from inetd.conf

Note

The following will be different if + request.

Starting from inetd.conf

Note

The following will be different if you use NIS, NIS+ or LDAP to distribute services maps.

Look at your /etc/services. What is defined at port 139/tcp. If nothing is defined then add a line like this:

netbios-ssn     139/tcp

similarly for 137/udp you should have an entry like:

netbios-ns	137/udp

Next edit your /etc/inetd.conf @@ -179,7 +178,7 @@ example of what you would not want to see would be: arguments, or you should use a script, and start the script from inetd.

Restart inetd, perhaps just send it a HUP. If you have installed an earlier version of nmbd then - you may need to kill nmbd as well.

Alternative: starting it as a daemon

To start the server as a daemon you should create + you may need to kill nmbd as well.

Alternative: starting it as a daemon

To start the server as a daemon you should create a script something like this one, perhaps calling it startsmb.

 		#!/bin/sh
@@ -191,7 +190,7 @@ example of what you would not want to see would be:
 		
To kill it send a kill signal to the processes 
 			nmbd and smbd.
Note
If you use the SVR4 style init system then 
 		you may like to look at the examples/svr4-startup
-		script to make Samba fit into that system.

Common Errors

“ + script to make Samba fit into that system.