• STAF is designed to put as few dependencies on the underlying system as possible. To that end we designed STAF to consume as little memory, disk, and CPU as possible. Some of these items (particularly disk space) aren’t nearly as important as they were several years ago. However, almost every new group that picks up STAF asks this very same question, “How much does STAF require?”. Along these same lines, we didn’t want to require any additional software on the system in order to run STAF. Writing STAF in Java would obviously require a JVM. Of the three resources previously listed, this has the largest impact on memory, and then CPU. Again, this isn’t as large an issue as it once was, as many/most systems today have a JVM. Nevertheless, we have many groups who are reluctant to put a JVM on their system, particularly those doing base OS testing (like the AIX and Linux Technology Center) teams, and they definitely don’t like being dependent on a JVM. For example, we have a group