I would like to be able to write AFICK, Perl, the afick database, and the afick configuration file to a CD-ROM and use a copy of the CD to check file content on other similarly configured machines. I would check only files/directories we create, not operating system files/dirs. The goal is to allow personnel in remote locations to compare some static content on each remote machine to a baseline which was created on a known secure machine, even if the remote machine has those files installed in a different directory than the original machine. Have you ever considered providing an option to write the db using unexpanded environmental variables instead of hard-coded full pathnames and to allow afick -k to substitute a new local value for that environmental variable? Any insights would be appreciated.