From e8ba8543e58f29eca5474b7f086671bfcf7c7994 Mon Sep 17 00:00:00 2001
From: Mike Hibler <mike@flux.utah.edu>
Date: Wed, 11 May 2005 21:52:44 +0000
Subject: [PATCH] Add a comment about how you really ought to follow the
 directions and create another admin account, lest you get yourself screwed

---
 doc/setup-db.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/setup-db.txt b/doc/setup-db.txt
index 19593431d4..f228c904d0 100644
--- a/doc/setup-db.txt
+++ b/doc/setup-db.txt
@@ -39,7 +39,10 @@ can use the sam actions. If you click on the dot, it will turn red, and you
 will have full administrator privileges; we call this 'going red dot'.
 Many of the procedures in this file require you to be in red dot mode.
 
-Now, we'll use the elabman user to bootstrap your own account. Log out of the
+Now, we'll use the elabman user to bootstrap your own account. Note that
+it is IMPORTANT that you create another account at this time since the
+elabman account does not have the power to perform certain actions that
+are required later (such as adding nodes to the testbed). So log out of the
 web interface, and use the 'Request Account' button to start a new project.
 Create a project that you can use for the faculty/students/staff involved in
 running your testbed - you can name it anything you'd like. Fill in your own
-- 
GitLab