Software Download Packages

This is the AT&T Software Technology ast software download site from AT&T Research. The AT&T AST OpenSource Software Collection provides an overview and Practical Reusable UNIX Software provides a historical perspective. You can join the ast and uwin mailgroups, or monitor the mail archives. The man page index contains most of the ast commands and library functions; command man pages are also available at runtime using the --man or --html option of any ast command.



Most AT&T ast software is licensed by the Eclipse Public License 1.0 (EPL-1.0). Before you download any packages you must signify your agreement to the terms of EPL-1.0 by entering a license agreement user name and password. This authorizes you to download. If you do not signify agreement then download access is denied. You will be prompted for the license agreement user name and password at download time. Every user will have the same user name and password, listed at the bottom of this copy of the License. When you click to download packages that require license authorization the browser will enter a username/password dialogue. Most browsers provide a cancel button -- click that and the license page, with username and password, will be displayed. If there is no cancel button then go to the EPL license page directly to determine the username/password to use, and then repeat the download process. Packages covered by licenses other than EPL-1.0 are controlled by a similar license-specific dialogue.

The software is divided into source and binary packages. Binary packages contain executables, libraries and headers targeted for a particular architecture. Source packages contain generic source that builds on all architectures. Each package is comprised of one or more components. A component is typically a library or a set of related commands managed by a single makefile. A package may depend on other packages, and a component may be contained in more than one package. The packages have been designed to share a common namespace, so they may be installed in a single directory structure. The only restriction is that dependent packages must be from the same release.

Download either source or binary packages, but not both -- a single cross-mounted copy of the source packages will build on all architectures.

Most packages are distributed as gzip-tar archives. If you don't have gunzip(1) or tar(1) then select the ratz(1) package for download. Some popular commands may be distributed as a standalone executable package that is simply a single gzipped executable. To unpack a standalone executable simply gunzip (or ratz -c) the download file into a bin directory and enable the execute bits. The ratz standalone package is not gzipped.

The download file size and checksums are for the original compressed files. Some browsers (e.g. IE) may decompress files as part of the download process and may not notify you of having done so. If this happens then the posted sizes and checksums will not match your downloaded files. This "feature" is controlled by the client side.

The INIT package is required by all but the standalone and self extracting archive packages. It contains the package(1) script that controls package installation and building.

The packages and instructions are probably very different than what you may have used before; the initial setup can be tedious. However, once that's done, downloading, updating, reading, building, testing and installing can all be scripted from the command line:

package setup # instead of CLICK to download -- you must still use the license agreement name and password
package make # if you have source packages
package test
package install DIRECTORY # if you want a separate installation

See the download menu on the left for more information.

Follow the package name links below to view the package descriptions, then use package setup (installing source or installing binaries) to download. package setup downloads the package closure (the package and prerequisites) and uses md5 checksums to determine out of date or compromised packages. Packages inside { . . . } are already included in the package to the right. Some binary releases may not be up to date; most likely we lost access to a machine of that type. Standalone and self extracting archive packages do not require the INIT package. To install a self extracting archive simply execute it (see uwin-base(1) and uwin-sear(1) for details.) To install a standalone executable gunzip (or ratz -c) the download file into a bin directory and enable the execute bits. To build or install a standalone package see the README within the tarball.

INIT - the package command with support scripts and utilities
ast-ast - the ast library, period
{ ast-make ast-ksh ksh ast-ast }   ast-base - ksh, ksh builtin commands, pax, nmake, tw, sfio, and ast libraries
ast-cql - cql, cia and incl commands and support libraries
ast-gpl - ast GPL open source commands and libraries
ast-jmake - ast nmake java support using a modified GPL jmake (javamake)
{ ksh }   ast-ksh - ksh and support libraries
{ ast-base ast-make ast-ksh ksh ast-ast ast-dss }   ast-open - ksh, pax, nmake, sfio, and ast open source commands and libraries
ast-sudoku - sudoku solvers
astsa - standalone ast library subset for standalone commands and libraries
boostexter - standalone boostexter command
cdt - standalone aso+cdt+vmalloc library
dwb - standalone documenters workbench command and libraries
ivsa - standalone iv interval / longest prefix match library
ksh - standalone AT&T ksh executable
mawl - standalone mawl command and libraries
ratz - standalone executable that reads gzipped tar archives
sfio - standalone sfio library
swift - swift big data collection, storage, analysis and display utilities
uwin - uwin package
uwin-base - UWIN base binary self extracting archive
uwin-dev - UWIN development binary self extracting archive
uwin-perl-58 - UWIN uwin perl 5.8
uwin - uwin package
vcodex - standalone vczip command and vcodex library
vmalloc - standalone aso+cdt+vmalloc library