Commit bf41c3bf authored by Russ Fish's avatar Russ Fish
Browse files

Document the use of prepare in Custom OS Images.

parent ba46c3d0
......@@ -1263,6 +1263,24 @@ default images as a base, goes like this:
good idea to reboot the node and make sure that everything is
running as you want it to when it comes up.
<li> When we make global images for everybody (like WINXP-SP1,
FBSD410-STD, and RHL90-STD), the final thing we do before grabbing
the image is log in as root and run the 'prepare' script. It
cleans out all of the other user accounts and per-experiment stuff
so a clean image is saved. Then at experiment swap-in time, the
Emulab management scripts create all of the accounts with
information drawn from the Emulab database.
This step is optional while creating custom images, except for
Windows images. Custom user images are limited to use within a
particular project, so it's a bit of an optimization for the
project user accounts to be already created in the custom image.
The saved stale account information is then overwritten by an
Emulab mechanism for updating the account information continuously
in an image. BUT, that mechanism is not yet implemented on
Windows, exposing the stale information there.
<li> Note the physical (pcXX) name of the machine used!
<li> Create an image descriptor and image using the
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment