as Xen. Ideally, the images are created "from scratch" using only commonly
available shell tools and access to the Internet. The specifications for building
the images are stored in a readable, configurable format that aim for a high degree
-of uniformity regardless of what the target image is. For instance there is a single
-syntax for installing packages to an image regardless of whether it is fedora,
+of uniformity regardless of what the target image is.
1. Download a release tarball from stacklet.com
- 3. cd src && python setup.py install
+ 4. python setup.py install (as root)
-The main shell script is /usr/bin/stackfactory
-Supporting files are in /usr/share/stacklet/
+The main shell script is /usr/bin/stackfactory (or /usr/local/bin/stackfactory)
+Supporting files are in /usr/share/stacklet/ (or /usr/local/share/stacklet/)
Output files will be stored in /var/stacklet/ unless overridden on the command line
+NOTE: The sample commands below assume that the share directory is
+/usr/share/stacklet whereas on some systems it will be /usr/local/share/stacklet/
+Please adjust as necessary!
+NOTE: stackfactory should run as root, use sudo if necessary.
Each stacklet build is driven by an xml file which is referred to as a spec.
The specs are stored under the specs directory which is further subdivided
among the various distributions that can be created. For instance,