- Timestamp:
- Nov 12, 2012, 5:38:52 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.5.x/docs/htmldocs/Samba3-HOWTO/compiling.html
r599 r736 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 42. How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Appendix.html" title="Part VI. Reference Section"><link rel="next" href="Portability.html" title="Chapter 43. 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 42. 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. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 42. How to Compile Samba"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 42. 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><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></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><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></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><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id44930 5">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id449311">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id449349">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id449521">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id449588">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id449717">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id449941">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id450191">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id450398">Alternative: Starting <span class="application">smbd</span> as a Daemon</a></span></dt></dl></dd></dl></div><p>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 42. How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Appendix.html" title="Part VI. Reference Section"><link rel="next" href="Portability.html" title="Chapter 43. 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 42. 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. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 42. How to Compile Samba"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 42. 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><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></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><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></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><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id449302">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id449308">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id449346">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id449518">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id449586">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id449715">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id449938">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id450188">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id450396">Alternative: Starting <span class="application">smbd</span> as a Daemon</a></span></dt></dl></dd></dl></div><p> 2 2 You can obtain the Samba source file from the 3 3 <a class="ulink" href="http://samba.org/" target="_top">Samba Web site</a>. To obtain a development version, 4 4 you can download Samba from Subversion or using <code class="literal">rsync</code>. 5 </p><div class="sect1" title="Access Samba Source Code via Subversion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id44930 5"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id449311"></a>Introduction</h3></div></div></div><p>6 <a class="indexterm" name="id44931 8"></a>5 </p><div class="sect1" title="Access Samba Source Code via Subversion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449302"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id449308"></a>Introduction</h3></div></div></div><p> 6 <a class="indexterm" name="id449316"></a> 7 7 Samba is developed in an open environment. Developers use a 8 8 Subversion to <span class="quote">“<span class="quote">checkin</span>”</span> (also known as … … 13 13 This chapter is a modified version of the instructions found at the 14 14 <a class="ulink" href="http://samba.org/samba/subversion.html" target="_top">Samba</a> Web site. 15 </p></div><div class="sect2" title="Subversion Access to samba.org"><div class="titlepage"><div><div><h3 class="title"><a name="id44934 9"></a>Subversion Access to samba.org</h3></div></div></div><p>15 </p></div><div class="sect2" title="Subversion Access to samba.org"><div class="titlepage"><div><div><h3 class="title"><a name="id449346"></a>Subversion Access to samba.org</h3></div></div></div><p> 16 16 The machine samba.org runs a publicly accessible Subversion 17 17 repository for access to the source code of several packages, 18 18 including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways 19 19 of accessing the Subversion server on this host. 20 </p><div class="sect3" title="Access via ViewCVS"><div class="titlepage"><div><div><h4 class="title"><a name="id4493 60"></a>Access via ViewCVS</h4></div></div></div><p>21 <a class="indexterm" name="id44936 8"></a>20 </p><div class="sect3" title="Access via ViewCVS"><div class="titlepage"><div><div><h4 class="title"><a name="id449357"></a>Access via ViewCVS</h4></div></div></div><p> 21 <a class="indexterm" name="id449365"></a> 22 22 You can access the source code via your favorite WWW browser. This allows you to access 23 23 the contents of individual files in the repository and also to look at the revision … … 27 27 Use the URL 28 28 <a class="ulink" href="http://viewcvs.samba.org/" target="_top">http://viewcvs.samba.org/</a>. 29 </p></div><div class="sect3" title="Access via Subversion"><div class="titlepage"><div><div><h4 class="title"><a name="id44939 2"></a>Access via Subversion</h4></div></div></div><p>30 <a class="indexterm" name="id449 400"></a>29 </p></div><div class="sect3" title="Access via Subversion"><div class="titlepage"><div><div><h4 class="title"><a name="id449390"></a>Access via Subversion</h4></div></div></div><p> 30 <a class="indexterm" name="id449398"></a> 31 31 You can also access the source code via a normal Subversion client. This gives you much more control over what 32 32 you can do with the repository and allows you to check out whole source trees and keep them up to date via … … 38 38 </p><p> 39 39 To gain access via anonymous Subversion, use the following steps. 40 </p><div class="procedure" title="Procedure 42.1. Retrieving Samba using Subversion"><a name="id44942 8"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p>40 </p><div class="procedure" title="Procedure 42.1. Retrieving Samba using Subversion"><a name="id449425"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> 41 41 Install a recent copy of Subversion. All you really need is a 42 42 copy of the Subversion client binary. … … 63 63 <strong class="userinput"><code>svn update</code></strong> 64 64 </pre><p> 65 </p></li></ol></div></div></div></div><div class="sect1" title="Accessing the Samba Sources via rsync and ftp"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4495 21"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>66 <a class="indexterm" name="id44952 9"></a>67 <a class="indexterm" name="id44953 6"></a>65 </p></li></ol></div></div></div></div><div class="sect1" title="Accessing the Samba Sources via rsync and ftp"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449518"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p> 66 <a class="indexterm" name="id449526"></a> 67 <a class="indexterm" name="id449533"></a> 68 68 <em class="parameter"><code>pserver.samba.org</code></em> also exports unpacked copies of most parts of the Subversion tree 69 69 at the Samba <a class="ulink" href="ftp://pserver.samba.org/pub/unpacked" target="_top">pserver</a> location and also … … 75 75 merging of local changes as Subversion does. <code class="literal">rsync</code> access is most convenient 76 76 for an initial install. 77 </p></div><div class="sect1" title="Verifying Samba's PGP Signature"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id44958 8"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>78 <a class="indexterm" name="id44959 6"></a>79 <a class="indexterm" name="id44960 3"></a>77 </p></div><div class="sect1" title="Verifying Samba's PGP Signature"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449586"></a>Verifying Samba's PGP Signature</h2></div></div></div><p> 78 <a class="indexterm" name="id449594"></a> 79 <a class="indexterm" name="id449600"></a> 80 80 It is strongly recommended that you verify the PGP signature for any source file before 81 81 installing it. Even if you're not downloading from a mirror site, verifying PGP signatures … … 88 88 <code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</code></strong> 89 89 </pre><p> 90 <a class="indexterm" name="id44964 7"></a>90 <a class="indexterm" name="id449644"></a> 91 91 The first file is the PGP signature for the Samba source file; the other is the Samba public 92 92 PGP key itself. Import the public PGP key with: … … 106 106 gpg: BAD signature from <span class="quote">“<span class="quote">Samba Distribution Verification Key</span>”</span> 107 107 </pre><p> 108 </p></div><div class="sect1" title="Building the Binaries"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id44971 7"></a>Building the Binaries</h2></div></div></div><p>109 <a class="indexterm" name="id44972 5"></a>110 <a class="indexterm" name="id4497 32"></a>108 </p></div><div class="sect1" title="Building the Binaries"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449715"></a>Building the Binaries</h2></div></div></div><p> 109 <a class="indexterm" name="id449723"></a> 110 <a class="indexterm" name="id449729"></a> 111 111 After the source tarball has been unpacked, the next step involves 112 112 configuration to match Samba to your operating system platform. … … 123 123 </pre><p> 124 124 </p><p> 125 <a class="indexterm" name="id4497 70"></a>125 <a class="indexterm" name="id449768"></a> 126 126 To build the binaries, run the program <strong class="userinput"><code>./configure 127 127 </code></strong> in the source directory. This should automatically … … 138 138 </pre><p> 139 139 </p><p> 140 <a class="indexterm" name="id44983 2"></a>140 <a class="indexterm" name="id449830"></a> 141 141 Execute the following create the binaries: 142 142 </p><pre class="screen"> … … 167 167 As you can see from this, building and installing Samba does not need to 168 168 result in disaster! 169 </p><div class="sect2" title="Compiling Samba with Active Directory Support"><div class="titlepage"><div><div><h3 class="title"><a name="id4499 41"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>169 </p><div class="sect2" title="Compiling Samba with Active Directory Support"><div class="titlepage"><div><div><h3 class="title"><a name="id449938"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p> 170 170 In order to compile Samba with ADS support, you need to have installed 171 171 on your system: … … 190 190 your LDAP libraries. Look in <code class="filename">config.log</code> to figure 191 191 out why and fix it. 192 </p><div class="sect3" title="Installing the Required Packages for Debian"><div class="titlepage"><div><div><h4 class="title"><a name="id4 50001"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>192 </p><div class="sect3" title="Installing the Required Packages for Debian"><div class="titlepage"><div><div><h4 class="title"><a name="id449999"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p> 193 193 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>libkrb5-dev</p></li><li class="listitem"><p>krb5-user</p></li></ul></div><p> 194 </p></div><div class="sect3" title="Installing the Required Packages for Red Hat Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id45002 7"></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>194 </p></div><div class="sect3" title="Installing the Required Packages for Red Hat Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id450025"></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> 195 195 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>krb5-workstation (for kinit)</p></li><li class="listitem"><p>krb5-libs (for linking with)</p></li><li class="listitem"><p>krb5-devel (because you are compiling from source)</p></li></ul></div><p> 196 196 </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 197 197 CDs to find which has them and install the files using your tool of choice. If in doubt 198 about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" title="SuSE Linux Package Requirements"><div class="titlepage"><div><div><h4 class="title"><a name="id45006 7"></a>SuSE Linux Package Requirements</h4></div></div></div><p>198 about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" title="SuSE Linux Package Requirements"><div class="titlepage"><div><div><h4 class="title"><a name="id450065"></a>SuSE Linux Package Requirements</h4></div></div></div><p> 199 199 SuSE Linux installs Heimdal packages that may be required to allow you to build 200 200 binary packages. You should verify that the development libraries have been installed on … … 207 207 packages where they are available. 208 208 </p></div></div></div><div class="sect1" title="Starting the smbd nmbd and winbindd"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="startingSamba"></a>Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></h2></div></div></div><p> 209 <a class="indexterm" name="id45011 6"></a>209 <a class="indexterm" name="id450113"></a> 210 210 You must choose to start <span class="application">smbd</span>, <span class="application">winbindd</span> and <span class="application">nmbd</span> either as daemons or from 211 211 <span class="application">inetd</span>. Don't try to do both! Either you can put … … 219 219 The main advantage of starting <span class="application">smbd</span> and <span class="application">nmbd</span> using the recommended daemon method 220 220 is that they will respond slightly more quickly to an initial connection request. 221 </p><div class="sect2" title="Starting from inetd.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id4501 91"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id450196"></a><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if221 </p><div class="sect2" title="Starting from inetd.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id450188"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id450194"></a><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if 222 222 you use NIS, NIS+, or LDAP to distribute services maps.</p></div><p>Look at your <code class="filename">/etc/services</code>. 223 223 What is defined at port 139/tcp? If nothing is defined, … … 228 228 netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 229 229 </pre><p> 230 </p><a class="indexterm" name="id45025 4"></a><p>230 </p><a class="indexterm" name="id450252"></a><p> 231 231 The exact syntax of <code class="filename">/etc/inetd.conf</code> 232 232 varies between UNIXes. Look at the other entries in inetd.conf 233 233 for a guide. 234 234 </p><p> 235 <a class="indexterm" name="id45027 3"></a>235 <a class="indexterm" name="id450271"></a> 236 236 Some distributions use xinetd instead of inetd. Consult the 237 237 xinetd manual for configuration information. … … 241 241 <code class="filename">/etc/inetd.conf</code> to make them consistent. 242 242 </p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 243 <a class="indexterm" name="id45030 9"></a>243 <a class="indexterm" name="id450306"></a> 244 244 On many systems you may need to use the 245 245 <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to specify … … 256 256 Restart <span class="application">inetd</span>, perhaps just send it a HUP, 257 257 like this: 258 <a class="indexterm" name="id45037 3"></a>258 <a class="indexterm" name="id450371"></a> 259 259 </p><pre class="screen"> 260 260 <code class="prompt">root# </code><strong class="userinput"><code>killall -HUP inetd</code></strong> 261 261 </pre><p> 262 </p></div><div class="sect2" title="Alternative: Starting smbd as a Daemon"><div class="titlepage"><div><div><h3 class="title"><a name="id45039 8"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>263 <a class="indexterm" name="id4504 12"></a>264 <a class="indexterm" name="id45041 8"></a>262 </p></div><div class="sect2" title="Alternative: Starting smbd as a Daemon"><div class="titlepage"><div><div><h3 class="title"><a name="id450396"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p> 263 <a class="indexterm" name="id450409"></a> 264 <a class="indexterm" name="id450416"></a> 265 265 To start the server as a daemon, you should create a script something 266 266 like this one, perhaps calling it <code class="filename">startsmb</code>. … … 281 281 <code class="filename">examples/svr4-startup</code> script to make Samba fit 282 282 into that system. 283 </p></div><div class="sect3" title="Starting Samba for Red Hat Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id45049 2"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p>283 </p></div><div class="sect3" title="Starting Samba for Red Hat Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id450490"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p> 284 284 Red Hat Linux has not always included all Samba components in the standard installation. 285 285 So versions of Red Hat Linux do not install the winbind utility, even though it is present … … 314 314 </pre><p> 315 315 Samba will be started automatically at every system reboot. 316 </p></div><div class="sect3" title="Starting Samba for Novell SUSE Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id45060 5"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p>316 </p></div><div class="sect3" title="Starting Samba for Novell SUSE Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id450602"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p> 317 317 Novell SUSE Linux products automatically install all essential Samba components in a default installation. 318 318 Configure your <code class="filename">smb.conf</code> file, then execute the following to start Samba:
Note:
See TracChangeset
for help on using the changeset viewer.
