From d59d442d9743f5aed75ffcfa8699c25e2dba65b6 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 28 Jun 2005 22:12:01 +0000 Subject: Update. (This used to be commit f568b682c01cf2134b39824ce5943952128dca29) --- docs/Samba3-HOWTO/TOSHARG-Compiling.xml | 62 +++++++++++++++------------------ 1 file changed, 28 insertions(+), 34 deletions(-) (limited to 'docs/Samba3-HOWTO') diff --git a/docs/Samba3-HOWTO/TOSHARG-Compiling.xml b/docs/Samba3-HOWTO/TOSHARG-Compiling.xml index f6536c8922..e110afaea5 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Compiling.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Compiling.xml @@ -8,6 +8,7 @@ 22 May 2001 18 March 2003 + June 2005 How to Compile Samba @@ -73,12 +74,11 @@ Use the URL 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. +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 @@ -103,10 +103,9 @@ To gain access via anonymous Subversion, use the following steps. Run the command - - - + svn co svn://svnanon.samba.org/samba/trunk samba. + @@ -116,26 +115,22 @@ To gain access via anonymous Subversion, use the following steps. - 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. + 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: - - - + Whenever you want to merge in the latest code changes, use the following command from within the Samba + directory: + svn update + @@ -172,6 +167,7 @@ To gain access via anonymous Subversion, use the following steps. GPG +PGP 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. @@ -193,31 +189,25 @@ With that said, go ahead and download the following files: PGP 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: - - &prompt;gpg --import samba-pubkey.asc - - and verify the Samba source code integrity with: - - &prompt;gzip -d samba-3.0.20.tar.gz &prompt;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 + - - gpg: BAD signature from Samba Distribution Verification Key - - @@ -225,6 +215,7 @@ example of what you would not want to see would be: autogen.sh +configure 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, @@ -441,6 +432,7 @@ netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd +/etc/inetd.conf The exact syntax of /etc/inetd.conf varies between UNIXes. Look at the other entries in inetd.conf @@ -479,6 +471,7 @@ netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd Restart inetd, perhaps just send it a HUP, like this: +killall &rootprompt;killall -HUP inetd @@ -491,6 +484,7 @@ netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd daemon +startsmb To start the server as a daemon, you should create a script something like this one, perhaps calling it startsmb. @@ -498,7 +492,7 @@ netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd #!/bin/sh /usr/local/samba/bin/smbd -D -/usr/local/samba/bin/winbindd +/usr/local/samba/bin/winbindd -B /usr/local/samba/bin/nmbd -D -- cgit