ignoring a and b drives

Bob Stockler bob at trebor.iglou.com
Thu Apr 29 10:41:14 PDT 2004


On Wed, Apr 28, 2004 at 10:40:33AM -0400, Jay R. Ashworth wrote:
| On Wed, Apr 28, 2004 at 08:31:51AM -0400, Kenneth Brody wrote:
| > "Jay R. Ashworth" wrote:
| > [...]
| > > > Or the more modern "PFDSK=drives" where "drives" is a list of the drive
| > > > letters you want filePro to scan.  (On *nix, PFDSK is a colon-separated
| > > > list of directories.)
| > > 
| > > At the risk of sounding stupid, "that you want filePro to scan" for
| > > *what*?  /fp/?  /filepro/?  `echo $PFDIR`?  /appl/?
| > 
| > It will scan those drives for key/data/index files, rather than the
| > old method of scanning all drives A: through Y: (DOS/Windows) or all
| > mounted filesystems (*nix).
| > 
| > ForEach DRIVE in $PFDSK
| > do
| >     using $DRIVE/$PFDIR/filepro/$PFNAME
| >     do
| >         LookFor key*, data*, index*
| >     done
| > done
| 
| IOW, it's looking for your current PFDIR underneath those drive
| letters/directories.  I assume that a) it scans them in order, and b)
| it stops scanning the first time it finds a valid PFDIR under one?

I'd guess "a" is correct, but it doesn't matter, because
in-so-far as "b", it scans all of them to find all of the
filePro files in the $PFDIR/filepro directories under them.

That's what lets one have the programs relating to a filePro
file on one HD, the key file another, the data file on another,
and the indexes on yet another, if one wanted to split them up
that much.

Having the key files on one HD and the indexes on another really
sped thing up on Tandy 6000 Xenix.

Bob

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).


More information about the Filepro-list mailing list