> The assign is done at open/close time, I suspect if one applicaiton assigns > the drive and leaves it assigned, then another application uses the drive, > then the the assign would be dropped after the second app closes the file.
Methinks the Right Thing To Do would be to add function to "mt" to allow it to reserve a drive (eg, "mt reserve /dev/st0") when a application wants on, and provide a release function when you're done with it (eg "mt release /dev/st0"). That would be generic enough to handle most of the Intel cases as well, but would suit us nicely(*). -- db * - setting an advisory lock or using flock/lockf() to create a lock file that other applications could query if need be.
