howto: Clarify differences when working from a tarball instead of Git.

[jelmer/samba4-debian.git] / howto.txt

diff --git a/howto.txt b/howto.txt
index 654ad658c8b795c3116840b0f4774a9eaa90b2bd..7b685372e669dc8d461835820908f0897243ce72 100644 (file)
--- a/howto.txt
+++ b/howto.txt
@@ -16,6 +16,13 @@ aimed at production use of Samba4.
 Step 1: download Samba4
 -----------------------
 
+If you have downloaded the Samba4 code via a tarball released from the
+samba.org website, Step 1 has already been completed for you.  For testing
+with the version released in the tarball, you may continue on to Step 2.  Note
+that the references below to the top-level directory named "samba4" will
+instead be based on the name of the tarball downloaded (e.g.
+"samba-4.0.0alpha3" for the tarball samba-4.0.0alpha3.tar.gz).
+
 There are 2 methods of doing this:
 
   method 1:  "rsync -avz samba.org::ftp/unpacked/samba_4_0_test/ samba4"
@@ -70,20 +77,17 @@ configure above to change this.
 Step 4: provision Samba4
 ------------------------
 
-The "provision" step sets up a basic user database. Make sure your smbscript
-binary is installed in a directory listed in your PATH environment variable.
-It is presumed it's available just like any other commands from your shell.
+The "provision" step sets up a basic user database. 
 Must be run as a user with permission to write to the install directory.
 
 ::
 
   # cd source
-  # ./setup/provision --realm=YOUR.REALM --domain=YOURDOM \
+  # bin/smbpython ./setup/provision --realm=YOUR.REALM --domain=YOURDOM \
   #  --adminpass=SOMEPASSWORD --server-role='domain controller'
 
-REMINDER: Add the "bin" directory of the path you installed to
-          (e.g. /usr/local/samba/bin) to your path, or the provision command
-          will not work.
+REMINDER: Use the path to smbpython, as the provision command
+          will not work with the system python.
 
 'YOURDOM' is the NT4 style domain name. 'YOUR.REALM' is your kerberos
 realm, which is typically your DNS domain name.