Chapter 42. 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

- +

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 @@ -12,13 +12,13 @@ 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 ViewCVS

- +

Access via ViewCVS

+ 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 @@ -26,8 +26,8 @@ listing between any two versions on the repository.

Use the URL http://viewcvs.samba.org/. -

Access via Subversion

- +

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 @@ -37,7 +37,7 @@ a Subversion client. Your distribution might include one, or you can download th sources from http://subversion.tigris.org/.

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

Procedure 42.1. Retrieving Samba using Subversion

+
Procedure 42.1. Retrieving Samba using Subversion
1. Install a recent copy of Subversion. All you really need is a copy of the Subversion client binary.
2. @@ -62,9 +62,9 @@ To gain access via anonymous Subversion, use the following steps.
```
 	svn update
 	
```
  -

Accessing the Samba Sources via rsync and ftp

- - +

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 @@ -74,9 +74,9 @@ To gain access via anonymous Subversion, use the following steps. 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

- - +

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. @@ -87,7 +87,7 @@ 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:

@@ -105,9 +105,9 @@ example of what you would not want to see would be:
 
 gpg: BAD signature from “Samba Distribution Verification Key”
 

-

Building the Binaries

- - +

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, @@ -122,7 +122,7 @@ gpg: BAD signature from “Samba Dis 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 @@ -137,7 +137,7 @@ gpg: BAD signature from “Samba Dis root# ./configure [... arguments ...]

- + Execute the following create the binaries:

 root#  make
@@ -166,7 +166,7 @@ gpg: BAD signature from “Samba Dis

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:

@@ -189,13 +189,13 @@ gpg: BAD signature from “Samba Dis 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:
+
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:
+
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
+ 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. @@ -206,7 +206,7 @@ gpg: BAD signature from “Samba Dis 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 @@ -218,7 +218,7 @@ gpg: BAD signature from “Samba Dis

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 +

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

@@ -227,12 +227,12 @@ gpg: BAD signature from “Samba Dis 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 @@ -240,7 +240,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 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 @@ -255,13 +255,13 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd

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

 root# killall -HUP inetd

Alternative: Starting smbd as a Daemon

- - +

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.

@@ -280,7 +280,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 	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 @@ -313,7 +313,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 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:

-- 
cgit v1.2.3