Its ready for download at Software Systems Research software.

All ast commands have builtin online documentation. For these commands the --man option produces a man page on the standard error. In addition, the --html option produces web man pages that have been posted here. Failing that, look in the man directory sibling to the bin directory where you found the command. As a final recourse, bug me to bring the item into the 21st century. Plans are to document the library interfaces in the interface headers.

Standalone binaries for most of the stuff described in ~gsf are available. Each item has specific download instructions.

If you have access to an AT&T research machine then the binaries may already be installed. Check /usr/common/ast/bin for the stable distribution and /home/gsf/arch/HOSTTYPE/bin for the the latest, where HOSTTYPE is defined by the output of the script /home/gsf/bin/package. If you reference binaries in my home bin directory then you may have to export LD_LIBRARY_PATH (or _RLD_PATH, depending on your OS conventions) with a reference to my home lib directory.

Some binaries are not available outside of AT&T. Others may be posted at one of these: Software Systems Research software, Practical Reusable UNIX Software.

Yes! Check out Software Systems Research software.

1. looks like it was written in 1985
2. looks like it was written by a technical writer
3. looks like it was written by M$
4. didn't help
5. all of the above

Lucent does a good job with the nmake documentation and newsletter. The AT&T and Lucent source trees have been split since 1995, so there will be some implementation differences.

Ok, so I'm the nth guy in line to attempt to name your architecture. The names evolve as vendors introduce binary incompatibilities. In some cases one host may support many architectures; most of these differences are determined by the compiler used. I try to keep the naming scheme from getting too pedantic, otherwise we'll end up with a different set of binaries for each machine in the house.