Merge from 0.1 branch:
	(491:492) Give sin account a shell on Linux.
	(493:496) Test installation on Mono.
	(497:498) Update working directory to requested revision when allocated.
Modified: trunk/Sin.Library/RootWorkingDirectory.cs
Modified: trunk/Sin.Setup/GettingStarted.txt

Modified: trunk/Sin.Library/RootWorkingDirectory.cs
--- trunk/Sin.Library/RootWorkingDirectory.cs	2005-08-28 12:07:06 UTC (rev 499)
+++ trunk/Sin.Library/RootWorkingDirectory.cs	2005-08-28 12:12:30 UTC (rev 500)
@@ -637,7 +637,7 @@
 				                        branch,
 				                        out currentRevision);
 				selectedWd.BeginAccess();
-				if (currentRevision < revision)
+				if (currentRevision != revision)
 				{
 					UpdateWorkingDirectory(selectedWd, revision);
 					currentRevision = revision;

Modified: trunk/Sin.Setup/GettingStarted.txt
--- trunk/Sin.Setup/GettingStarted.txt	2005-08-28 12:07:06 UTC (rev 499)
+++ trunk/Sin.Setup/GettingStarted.txt	2005-08-28 12:12:30 UTC (rev 500)
@@ -24,7 +24,7 @@
 
 If you created a new repository, or your existing repository doesn't have it, then also create the directory "branches". If you used an existing repository then you need to copy all your existing branches into the checkin directory. For the main branch named trunk, copy it to checkin/trunk. Copy the other branches so they are present under checkin/branches/.
 
-3d. Run the configuration tool called Sin Setup (on Windows) in order to configure Sin or create the configuration files manually. Read Sin.pdf for information on how to create the configuration files. Sin.Configuration.Templates.zip in the distribution contain template configuration files which can be used as a starting point.
+3d. Run the configuration tool called Sin Setup (on Windows) in order to configure Sin or create the configuration files manually. Read Sin.pdf for information on how to create the configuration files. Sin.Configuration.Templates.zip in the distribution contain template configuration files which can be used as a starting point. N.B. When using XSP on Linux and running Sin under a non-root account (which is strongly recommended), remember to configure Sin.Control to use a port higher than 1024.
 
 3e. Give the account under which the Sin services run, access to the repository. On Windows, give the account Full Control access to the repository except for the conf directory for which the account should have only Read access, and the hooks directory for which the account should have Read & Execute access.
 
@@ -34,7 +34,7 @@
 
 Add an account for Sin:
 
-	# adduser -g sin -s /bin/false sin
+	# adduser -g sin sin
 
 3f. Set up the repository hooks. Create a text file named /svn/hooks/pre-commit and put the following in it:
 
@@ -87,3 +87,5 @@
 3m. Start Sin.
 
 	# su -l sin -c "cd /sin && mono Sin.Control.exe start"
+
+3n. Test the installation. Go to http://<machine IP>:<XSP port>/Integrator/Integrator.asmx. A webservice should be displayed. Click Ping in the Methods group, then click Test Form, and then click Invoke. An XML document containing the word false should be displayed. If not, try looking in sin/data/Integrator/Integrator.log for possible errors. Go to http://<machine IP>:<XSP port>. A website should be displayed. If not, try looking in sin/data/IntegrationManager/Integration Manager.log for possible errors.