Chapter 41. How to Compile Samba

+You can obtain the Samba source file from the +Samba Web site. To obtain a development version, +you can download Samba from Subversion or using rsync. +

Access Samba Source Code via Subversion

Introduction

+ +Samba is developed in an open environment. Developers use a +Subversion to “checkin” (also known as +“commit”) new source code. Samba's various Subversion branches can +be accessed via anonymous Subversion using the instructions +detailed in this chapter. +

+This chapter is a modified version of the instructions found at the +Samba Web site. +

Subversion Access to samba.org

+The machine samba.org runs a publicly accessible Subversion +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 Subversion server on this host. +

Access via SVNweb

+ +You can access the source code via your favorite WWW browser. This allows you to access +the contents of individual files in the repository and also to look at the revision +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://svnweb.samba.org/. +

Access via Subversion

+ +You can also access the source code via a normal Subversion client. This gives you much more control over what +you can do with the repository and allows you to check out whole source trees and keep them up to date via +normal Subversion commands. This is the preferred method of access if you are a developer and not just a +casual browser. +

In order to be able to download the Samba sources off Subversion, you need +a Subversion client. Your distribution might include one, or you can download the +sources from http://subversion.tigris.org/. +

+To gain access via anonymous Subversion, use the following steps. +

Procedure 41.1. Retrieving Samba using Subversion

+ Install a recent copy of Subversion. All you really need is a + copy of the Subversion client binary. +
+ Run the command +
```
+	svn co svn://svnanon.samba.org/samba/trunk samba.
+	
```
+
+ This will create a directory called samba containing the + latest Samba source code (usually the branch that is going to be the next major release). This + currently corresponds to the 3.1 development tree. +
+ Subversion branches other then trunk can be obtained by adding branches/BRANCH_NAME to the URL you check + out. A list of branch 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 command: +
```
+	svn co svn://svnanon.samba.org/samba/branches/SAMBA_3_0 samba_3.
+	
```
+
+ Whenever you want to merge in the latest code changes, use the following command from within the Samba + directory: +
```
+	svn update
+	
```
+

Accessing the Samba Sources via rsync and ftp

+ + + pserver.samba.org also exports unpacked copies of most parts of the Subversion tree + at the Samba pserver location and also + via anonymous rsync at the Samba rsync server location. I recommend using rsync rather + than ftp, because rsync is capable of compressing data streams, but it is also more useful than FTP because + during a partial update it will transfer only the data that is missing plus a small overhead. See the rsync home page for more info on rsync. +

+ The disadvantage of the unpacked trees is that they do not support automatic + merging of local changes as Subversion does. rsync access is most convenient + for an initial install. +

Verifying Samba's PGP Signature

+ + +It is 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 standard reflex. Many people today use the GNU GPG tool set in place of PGP. +GPG can substitute for PGP. +

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

+$ wget http://us1.samba.org/samba/ftp/samba-3.0.20.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-3.0.20.tar.gz
+$ gpg --verify samba-3.0.20.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”
+

Building the Binaries

+ + + After the source tarball has been unpacked, the next step involves + configuration to match Samba to your operating system platform. + If your source directory does not contain the configure script, + it is necessary to build it before you can continue. Building of + the configure script requires the correct version of the autoconf + tool kit. Where the necessary version of autoconf is present, + the configure script can be generated by executing the following: +

+root#  cd samba-3.0.20/source
+root#  ./autogen.sh
+

+ + To build the binaries, 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 first run: +

+root# ./configure --help
+

+ This will help you to see what special options can be enabled. Now execute + ./configure with any arguments it might need: +

+root# ./configure [... arguments ...]
+

+ + Execute the following create the binaries: +

+root#  make
+

+ Once it is successfully compiled, you can execute the command shown here to + install the binaries and manual pages: +

+root#  make install
+

+ Some people prefer to install binary files and man pages separately. If this is + your wish, the binary files can be installed by executing: +

+root#  make installbin
+

+ The man pages can be installed using this command: +

+root#  make installman
+

+ Note that if you are upgrading from a previous version of Samba the old + versions of the binaries will be renamed with an “.old” extension. + You can go back to the previous version by executing: +

+root#  make revert
+

+ As you can see from this, building and installing Samba does not need to + result in 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 or Heimdal Kerberos development libraries + (either install from the sources or use a package). +
+ The OpenLDAP development libraries. +

+ If your Kerberos libraries are in a nonstandard location, then + remember to add the configure option + --with-krb5=DIR. +

+ After you run configure, make sure that the + include/config.h it generates contain lines like this: +

+#define HAVE_KRB5 1
+#define HAVE_LDAP 1
+

+ If it does not, 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 Red Hat Linux

On Red Hat Linux, 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.

If these files are not installed on your system, you should check the installation + CDs to find which has them and install the files using your tool of choice. If in doubt + about what tool to use, refer to the Red Hat Linux documentation.

SuSE Linux Package Requirements

+ SuSE Linux installs Heimdal packages that may be required to allow you to build + binary packages. You should verify that the development libraries have been installed on + your system. +

+ SuSE Linux Samba RPMs support Kerberos. Please refer to the documentation for + your SuSE Linux system for information regarding SuSE Linux specific configuration. + Additionally, SuSE is very active in the maintenance of Samba packages that provide + the maximum capabilities that are available. You should consider using SuSE-provided + packages where they are available. +

Starting the smbd nmbd and winbindd

+ + You must choose to start smbd, winbindd 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 xinetd, or you + can start them as daemons either from the command-line or in + /etc/rc.local. See the man pages for details on the + command line options. Take particular care to read the bit about what user + you need to have to start 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 + 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 and add two lines like this: +

+netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd 
+netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 
+

+ The exact syntax of /etc/inetd.conf + varies between UNIXes. Look at the other entries in inetd.conf + for a guide. +

+ + Some distributions use xinetd instead of inetd. Consult the + xinetd manual for configuration information. +

Note

Some UNIXes already have entries like netbios_ns + (note the underscore) in /etc/services. + You must edit /etc/services or + /etc/inetd.conf to make them consistent. +

Note

+ + On many systems you may need to use the + interfaces option in smb.conf to specify + the IP address and netmask of your interfaces. Run + ifconfig as root if you do + not know what the broadcast is for your net. nmbd tries + to determine it at runtime, but fails on some UNIXes. +

Warning

+ Many UNIXes only accept around five parameters on the command + line in inetd.conf. This means you shouldn't + use spaces between the options and arguments, or you should use + a script and start the script from inetd. +

+ Restart inetd, perhaps just send it a HUP, + like this: + +

+root# killall -HUP inetd
+

Alternative: Starting smbd 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
+/usr/local/samba/sbin/smbd -D 
+/usr/local/samba/sbin/winbindd -B
+/usr/local/samba/sbin/nmbd -D 
+

+ Make it executable with chmod +x startsmb. +

+ You can then run startsmb by hand or execute + it from /etc/rc.local. +

+ To kill it, send a kill signal to the processes nmbd and smbd. +

Note

+ If you use the SVR4-style init system, you may like to look at the + examples/svr4-startup script to make Samba fit + into that system. +

Starting Samba for Red Hat Linux

+ Red Hat Linux has not always included all Samba components in the standard installation. + So versions of Red Hat Linux do not install the winbind utility, even though it is present + on the installation CDROM media. Check to see if the winbindd is present + on the system: +

+root#  ls /usr/sbin/winbindd
+/usr/sbin/winbindd
+

+ This means that the appropriate RPM package was installed. The following response means + that it is not installed: +

+/bin/ls: /usr/sbin/winbind: No such file or directory
+

+ In this case, it should be installed if you intend to use winbindd. Search + the CDROM installation media for the samba-winbind RPM and install it following Red Hat + guidelines. +

+ The process for starting Samba will now be outlined. Be sure to configure Samba's smb.conf + file before starting Samba. When configured, start Samba by executing: +

+root#  service smb start
+root#  service winbind start
+

+ These steps will start nmbd, smbd and winbindd. +

+ To ensure that these services will be automatically restarted when the system is rebooted + execute: +

+root#  chkconfig smb on
+root#  chkconfig winbind on
+

+ Samba will be started automatically at every system reboot. +

Starting Samba for Novell SUSE Linux

+ Novell SUSE Linux products automatically install all essential Samba components in a default installation. + Configure your smb.conf file, then execute the following to start Samba: +

+root#  rcnmb start
+root#  rcsmb start
+root#  rcwinbind start
+

+ Now execute these commands so that Samba will be started automatically following a system + reboot: +

+root#  chkconfig nmb on
+root#  chkconfig smb on
+root#  chkconfig winbind on
+

+ The Samba services will now be started automatically following a system reboot. +