~ubuntu-branches/ubuntu/lucid/samba/lucid-proposed

<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�36.�How to Compile Samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.64.1"><link rel="home" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Appendixes"><link rel="previous" href="Appendix.html" title="Part�VI.�Appendixes"><link rel="next" href="Portability.html" title="Chapter�37.�Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�36.�How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Appendixes</th><td width="20%" align="right">�<a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter�36.�How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2597344">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2597350">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2597391">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2597566">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2597632">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2597770">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2597954">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2598117">Starting the smbd and nmbd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2598209">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2598414">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p>

<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�38.�How to Compile Samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Appendixes"><link rel="prev" href="Appendix.html" title="Part�VI.�Appendixes"><link rel="next" href="Portability.html" title="Chapter�39.�Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�38.�How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Appendixes</th><td width="20%" align="right">�<a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter�38.�How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2618614">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2618620">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2618662">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2618836">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2618902">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2619040">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2619266">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2619428">Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2619521">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2619726">Alternative: Starting <span class="application">smbd</span> as a Daemon</a></span></dt></dl></dd></dl></div><p>

You can obtain the Samba source from the

<a href="http://samba.org/" target="_top">Samba Website.</a> To obtain a development version,

you can download Samba from Subversion or using <span><b class="command">rsync</b></span>.

</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2597344"></a>Access Samba Source Code via Subversion</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597350"></a>Introduction</h3></div></div><div></div></div><p>

</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618614"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618620"></a>Introduction</h3></div></div></div><p>

Samba is developed in an open environment. Developers use a

Subversion to “<span class="quote"><span class="emphasis"><em>checkin</em></span></span>” (also known as

“<span class="quote"><span class="emphasis"><em>commit</em></span></span>”) new source code. Samba's various Subversion branches can

</p><p>

This chapter is a modified version of the instructions found at the

<a href="http://samba.org/samba/subversion.html" target="_top">Samba</a> web site.

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597391"></a>Subversion Access to samba.org</h3></div></div><div></div></div><p>

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618662"></a>Subversion Access to samba.org</h3></div></div></div><p>

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:

</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2597405"></a>Access via SVNweb</h4></div></div><div></div></div><p>

</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2618675"></a>Access via SVNweb</h4></div></div></div><p>

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

</p><p>

Use the URL:

<a href="http://svnweb.samba.org/" target="_top">http://svnweb.samba.org/</a>

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2597439"></a>Access via Subversion</h4></div></div><div></div></div><p>

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2618709"></a>Access via Subversion</h4></div></div></div><p>

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 checkout whole source trees

sources from <a href="http://subversion.tigris.org/" target="_top">http://subversion.tigris.org/</a>.

</p><p>

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

</p><div class="procedure"><p class="title"><b>Procedure�36.1.�Retrieving Samba using Subversion</b></p><ol type="1"><li><p>

</p><div class="procedure"><a name="id2618742"></a><p class="title"><b>Procedure�38.1.�Retrieving Samba using Subversion</b></p><ol type="1"><li><p>

Install a recent copy of Subversion. All you really need is a

copy of the Subversion client binary.

</p></li><li><p>

the following command from within the Samba directory:

</p><p>

<b class="userinput"><tt>svn update</tt></b>

</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2597566"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div><div></div></div><p>

</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618836"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>

<i class="parameter"><tt>pserver.samba.org</tt></i> also exports unpacked copies of most parts of the Subversion

tree at the Samba <a href="ftp://pserver.samba.org/pub/unpacked" target="_top">pserver</a>

location and also via anonymous rsync at the Samba

The disadvantage of the unpacked trees is that they do not support automatic

merging of local changes like Subversion does. <span><b class="command">rsync</b></span> access is most convenient

for an initial install.

</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2597632"></a>Verifying Samba's PGP Signature</h2></div></div><div></div></div><p>

</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618902"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>

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.

<tt class="prompt">$ </tt><b class="userinput"><tt>wget http://us1.samba.org/samba/ftp/samba-3.0.0.tar.asc</tt></b>

<tt class="prompt">$ </tt><b class="userinput"><tt>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</tt></b>

</pre><p>

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:

</p><pre class="screen">

103

example of what you would not want to see would be:

104

</p><pre class="screen">

105

gpg: BAD signature from “<span class="quote"><span class="emphasis"><em>Samba Distribution Verification Key</em></span></span>”

106

</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2597770"></a>Building the Binaries</h2></div></div><div></div></div><p>

107

108

To build the binaries, first run the program <b class="userinput"><tt>./configure

106

</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619040"></a>Building the Binaries</h2></div></div></div><p>

107

108

After the source tarball has been unpacked, the next step involves

109

configuration to match Samba to your operating system platform.

110

If your source directory does not contain the <span><b class="command">configure</b></span> script

111

it is necessary to build it before you can continue. Building of

112

the configure script requires the correct version of the autoconf

113

tool kit. Where the necessary version of autoconf is present,

114

the configure script can be generated by executing the following:

115

</p><pre class="screen">

116

<tt class="prompt">root# </tt> cd samba-3.0.0

117

<tt class="prompt">root# </tt> ./autogen.sh

118

</pre><p>

119

</p><p>

120

121

To build the binaries, run the program <b class="userinput"><tt>./configure

109

122

</tt></b> in the source directory. This should automatically

110

123

configure Samba for your operating system. If you have unusual

111

124

needs, then you may wish to run</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>./configure --help

112

125

</tt></b></pre><p>first to see what special options you can enable. Now execute <b class="userinput"><tt>./configure</tt></b> with any arguments it might need:</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>./configure <i class="replaceable"><tt>[... arguments ...]</tt></i></tt></b></pre><p>Executing</p><p>

113

126

114

127

</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make</tt></b></pre><p>will create the binaries. Once it is successfully

115

128

compiled you can use</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make install</tt></b></pre><p>to install the binaries and manual pages. You can

116

129

separately install the binaries and/or man pages using</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make installbin

119

132

of Samba you might like to know that the old versions of

120

133

the binaries will be renamed with an “<span class="quote"><span class="emphasis"><em>.old</em></span></span>” extension. You

121

134

can go back to the previous version with</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make revert

122

</tt></b></pre><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597954"></a>Compiling Samba with Active Directory Support</h3></div></div><div></div></div><p>In order to compile Samba with ADS support, you need to have installed

135

</tt></b></pre><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619266"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>In order to compile Samba with ADS support, you need to have installed

123

136

on your system:</p><div class="itemizedlist"><ul type="disc"><li><p>The MIT or Heimdal Kerberos development libraries

124

137

(either install from the sources or use a package).</p></li><li><p>The OpenLDAP development libraries.</p></li></ul></div><p>If your Kerberos libraries are in a non-standard location, then

125

138

remember to add the configure option

130

143

#define HAVE_LDAP 1

131

144

</pre><p>If it does not, configure did not find your KRB5 libraries or

132

145

your LDAP libraries. Look in <tt class="filename">config.log</tt> to figure

133

out why and fix it.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2598020"></a>Installing the Required Packages for Debian</h4></div></div><div></div></div><p>On Debian, you need to install the following packages:</p><p>

146

out why and fix it.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619332"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>

134

147

</p><div class="itemizedlist"><ul type="disc"><li><p>libkrb5-dev</p></li><li><p>krb5-user</p></li></ul></div><p>

135

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2598047"></a>Installing the Required Packages for Red Hat Linux</h4></div></div><div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p>

148

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619358"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p>

136

149

</p><div class="itemizedlist"><ul type="disc"><li><p>krb5-workstation (for kinit)</p></li><li><p>krb5-libs (for linking with)</p></li><li><p>krb5-devel (because you are compiling from source)</p></li></ul></div><p>

137

150

</p><p>in addition to the standard development environment.</p><p>If these files are not installed on your system, you should check the installation

138

151

CDs to find which has them and install the files using your tool of choice. If in doubt

139

about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2598091"></a>SuSE Linux Package Requirements</h4></div></div><div></div></div><p>SuSE Linux installs Heimdal packages that may be required to allow you to build

152

about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619403"></a>SuSE Linux Package Requirements</h4></div></div></div><p>SuSE Linux installs Heimdal packages that may be required to allow you to build

140

153

binary packages. You should verify that the development libraries have been installed on

141

154

your system.

142

155

</p><p>SuSE Linux Samba RPMs support Kerberos. Please refer to the documentation for

144

157

Additionally, SuSE are very active in the maintenance of Samba packages that provide

145

158

the maximum capabilities that are available. You should consider using SuSE provided

146

159

packages where they are available.

147

</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598117"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div><div></div></div><p>

148

160

</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619428"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div></div><p>

161

149

162

You must choose to start <span class="application">smbd</span> and <span class="application">nmbd</span> either

150

163

as daemons or from <span class="application">inetd</span>. Don't try

151

164

to do both! Either you can put them in <tt class="filename">

159

172

Samba. In many cases, you must be root.</p><p>The main advantage of starting <span class="application">smbd</span>

160

173

and <span class="application">nmbd</span> using the recommended daemon method

161

174

is that they will respond slightly more quickly to an initial connection

162

request.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598209"></a>Starting from inetd.conf</h3></div></div><div></div></div><a class="indexterm" name="id2598215"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if

175

request.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619521"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2619527"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if

163

176

you use NIS, NIS+ or LDAP to distribute services maps.</p></div><p>Look at your <tt class="filename">/etc/services</tt>.

164

177

What is defined at port 139/tcp? If nothing is defined,

165

178

then add a line like this:</p><pre class="programlisting">netbios-ssn 139/tcp</pre><p>Similarly for 137/udp, you should have an entry like:</p><pre class="programlisting">netbios-ns 137/udp</pre><p>Next, edit your <tt class="filename">/etc/inetd.conf</tt>

169

182

</pre><p>The exact syntax of <tt class="filename">/etc/inetd.conf</tt>

170

183

varies between UNIXes. Look at the other entries in inetd.conf

171

184

for a guide. </p><p>

172

185

173

186

Some distributions use xinetd instead of inetd. Consult the

174

187

xinetd manual for configuration information.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Some UNIXes already have entries like netbios_ns

175

188

(note the underscore) in <tt class="filename">/etc/services</tt>.

176

189

You must edit <tt class="filename">/etc/services</tt> or

177

190

<tt class="filename">/etc/inetd.conf</tt> to make them consistent.

178

191

</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>

179

192

180

193

On many systems you may need to use the

181

<a class="indexterm" name="id2598338"></a>interfaces option in <tt class="filename">smb.conf</tt> to specify the IP

194

<a class="indexterm" name="id2619649"></a>interfaces option in <tt class="filename">smb.conf</tt> to specify the IP

182

195

address and netmask of your interfaces. Run

183

196

<span class="application">ifconfig</span>

184

197

as root if you do not know what the broadcast is for your

191

204

from <span><b class="command">inetd</b></span>.</p></div><p>Restart <span class="application">inetd</span>, perhaps just send

192

205

it a HUP. </p><pre class="screen">

193

206

<tt class="prompt">root# </tt><b class="userinput"><tt>killall -HUP inetd</tt></b>

194

</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598414"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div><div></div></div><p>

195

207

</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619726"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>

208

196

209

To start the server as a daemon, you should create

197

210

a script something like this one, perhaps calling

198

211

it <tt class="filename">startsmb</tt>.</p><pre class="programlisting">

205

218

</p><p>To kill it, send a kill signal to the processes

206

219

<span class="application">nmbd</span> and <span class="application">smbd</span>.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>If you use the SVR4 style init system,

207

220

you may like to look at the <tt class="filename">examples/svr4-startup</tt>

208

script to make Samba fit into that system.</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Appendix.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="Appendix.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="Portability.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part�VI.�Appendixes�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�37.�Portability</td></tr></table></div></body></html>

221

script to make Samba fit into that system.</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Appendix.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="Appendix.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="Portability.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part�VI.�Appendixes�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�39.�Portability</td></tr></table></div></body></html>

Older »