1 files changed, 50 insertions, 6 deletions

diff --git a/INSTALL.md b/INSTALL.md
index fdbc8e0..5c18160 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -12,6 +12,50 @@ risk.  It's been used to set up a few freshly installed servers though.
 It should work on recent Debian based Linux distros.
 
 
+For those in a hurry.
+---------------------
+
+On a recent Debian based Linux (Debian, Devuan, Ubuntu, Mint, ...)
+terminal, run the following command -
+
+./InstallItAll.sh
+
+This will install the prerequisites (MariaDB, monit, MONO, tmux,
+uuid-runtime); create a database in MariaDB called opensim_SC and a
+database user called opensim_SC with a random password; add a Linux user
+to your system called opensimsc; create the /opt/opensim_SC directory to
+run it all from; copy everything to /opt/opensim_SC/opensim-SC_0.9.0.1;
+setup the directory structure needed to run it all; create some default
+configuration files; build OpenSim-SC; and finally change ownership and
+file permissions for everything.
+
+Next go to /opt/opensim_SC/current/scripts/install and run -
+
+sudo ./create_sim.sh
+
+This will create a randomly named sim at a randomly chosen position.  Or
+for something less random -
+
+sudo ./create_sim.sh "My new sim" "1234,5678"
+
+At this point /opt/opensim_SC/config/config.ini will be a symlink
+pointing to config_localhost.ini, which is for a standalone sim.  If you
+want your new random sim to be part of Infinite Grid (IG) or Misfitz Grid
+(MG) then you'll have to change that syml/ink to point to config_IG.ini or
+config_MG.ini respectively.
+
+/opt/opensim_SC/config/sim01 now contains the aactual configuration of
+your randomly created sim.  Edit the .xml file to make that sim a little
+less random.
+
+Finally run -
+
+cd /opt/opensim_SC/config/sim01
+./start-sim
+
+To actually startup your sim.
+
+
 The directory layout.
 ---------------------
 
@@ -40,7 +84,7 @@ scripts		Various Linux scripts for managing OpenSim.
 
 share           No idea really.
 
-Also, the installation script moves the following directories from the
+Also, the installation script copies the following directories from the
 example directory, to outside of this main directory, they are all used
 for writing various things.  Makes it easy to upgrade, and separates them
 from actual executable stuff.
@@ -51,7 +95,7 @@ backups		All sim and inventory backups are stored here.
 
 caches          Various cached things.
 
-config          All your configurtion files.
+config          All your configuration files.
 
 db              If you are not using MySQL, your data lives here.
 
@@ -87,17 +131,17 @@ Creating sims.
 A separate script is here for sim creation, you can use it to create many
 sims.  You will need -
 
-Your host name, or it could be your IP, we will use "sims.example.net".
-
 A name for your sim, we will use "My new sim".  It should be unique on
 the grid.
 
+Your host name, or it could be your IP, we will use "sims.example.net".
+
 A location for your sim, we will use "1234,5678".  You can use the
 Infinite Grid web based map to poke around and find a good location. 
 Choose an empty spot.
 
 Once you have all that information sorted out, run this script from the
-installed scripts directory -
+scripts/install directory -
 
 ./create_sim.sh "My new sim" "1234,5678" "sims.example.net"
 
@@ -152,7 +196,7 @@ This attempts to use only one copy of the OS install for all sims.  We
 are running one instance of OS for each sim though, as this prevents one
 sim crashing from bringing down the others.  OS however really wants to
 write data to directories within it's own bin directory.  I'm not at all
-certian if that data can be shared.  For the same reason, so far I've
+certain if that data can be shared.  For the same reason, so far I've
 not been able to get to the point where we can make the OS directory
 read only.  This complicates things during upgrades.