diff --git a/doc/html/faq.shtml b/doc/html/faq.shtml
index 38006705c190d8b4d51f4099b0998be15bccce9b..fd802fe753c7ac9d4ac2ff3d37abe77e781e9853 100644
--- a/doc/html/faq.shtml
+++ b/doc/html/faq.shtml
@@ -502,6 +502,24 @@ for this due to it's improved support for multiple slurmd daemons.
 See the
 <a href="programmer_guide.shtml#multiple_slurmd_support">Programmers Guide</a>
 for more details about configuring multiple slurmd support.
+<p>In order to emulate a really large cluster, it can be more 
+convenient to use a single <i>slurmd</i> daemon. 
+That daemon will not be able to launch many tasks, but can 
+suffice for developing or testing scheduling software.
+<ol>
+<li>Execute the <i>configure</i> program with your normal options.</li>
+<li>Add the line "<i>#define HAVE_FRONT_END 1</i>" to the resulting
+<i>config.h</i> file.</li>
+<li>Build and install SLURM in the usual manner.</li>
+<li>In <i>slurm.conf</i> define the desired node names (arbitrary
+names used only by SLURM) as <i>NodeName</i> along with the actual
+address of the <b>one</b> physical node in <i>NodeHostname</i>.
+Up to 64k nodes can be configured in this virtual cluster.</li>
+<li>Start your <i>slurmctld</i> and one <i>slurmd</i> daemon.</li>
+<li>Create job allocations as desired, but <b>do not run job steps
+with more than a couple of tasks.</b> Doing so may result in the 
+<i>slurmd</i> daemon exhausting its memory and failing.</li>
+</ol>
 
 <p><a name="extra_procs"><b>15. Can SLURM emulate nodes with more
 resources than physically exist on the node?</b></a><br>
@@ -581,6 +599,6 @@ about these options.
 
 <p class="footer"><a href="#top">top</a></p>
 
-<p style="text-align:center;">Last modified 9 May 2007</p>
+<p style="text-align:center;">Last modified 14 May 2007</p>
 
 <!--#include virtual="footer.txt"-->