1 mike  1.1.2.1 
 2                   1. VXWorks has no fork/exec semantics.
 3               
 4                   2. VXWorks has no user database maniuplation.
 5               
 6                   3. VXWorks has no file ownership management.

 7 mike  1.1.2.2 
 8                   4. VXWorks has no popen(), but it is only needed in one test.
 9               
10                   5. floating points types are broken (printf does not work and they sometimes
11                      exhibit strange behavior).
12               
13                   6. The vxworks target start with its clock set to epoch.
14               

15 mike  1.1.2.3     7. access() is broken on VxWorks. It is defined and links but always
16                      return -1.