Some people at the AFS BOF at LISA mentioned adm and emt didn't compile for them on systems we use it on, so I uploaded current versions of both (and a new copy of the time stamp database source for use with emt) to ftp.andrew.cmu.edu; You can find them in: ftp://ftp.andrew.cmu.edu/pub/adm/adm-042.tar.gz ftp://ftp.andrew.cmu.edu/pub/emt/emt-3.4.1.tar.gz ftp://ftp.andrew.cmu.edu/pub/emt/tsdb-019.tar.gz For those who don't know: 1) adm provides a priviledge delegation service to allow distribution of administration control to a wider yet finer grain than AFS allows, and has been extended (here) for use with other services. It uses scheme and an embedded scheme interpreter to allow new commands to be defined; New functionality can be written in C and linked into the server. It requires AFS currently for lwp, rx, and rxkad, though it is likely that in the near future a version which links against the versions of those libraries which come with Arla will be made available (with more limited backend functionality, most probably, since Arla lacks some of the API that AFS has and hence when linking only against free libraries some features currently available will not be possible) 2) emt provides a mechanism for controlling software versioning on a per-package, per-release (e.g. a "beta" level, a "gamma" level, other levels), per-tree (a "local" tree for software you provide users, a "contributed" tree for user-supported software) and per-system ("sun4x_56", "i386_linux2") level, though these bindings are not rigorous and can be modified through use of the emt configuration file. It can use the time stamp database to help with version management. Traditionally it is used with depot (also available from the andrew ftp site, though that has not yet been updated to reflect our most current code) and adm to provide a simple front end for version management. Questions and comments about adm and emt may be sent to [EMAIL PROTECTED]
