ignoring a and b drives

[Bob Stockler]

On Thu, Apr 29, 2004 at 05:20:27PM -0400, Jay R. Ashworth wrote:
| On Thu, Apr 29, 2004 at 05:07:02PM -0400, Kenneth Brody wrote:
| > [...]
| > > > Only $PFDATA$PFDIR/filepro files will show up, as only key/data/index.*
| > > > files can be elsewhere.
| > > 
| > > That sounds like it answers my question, but I don't think it actually
| > > does.  If PFDATA=/u1:/u2, then will both database1 and database2
| > > appear?
| > 
| > Only if they are both in the "/u1:/u2/appl/filepro" directory.  ;-)
| 
| You said that $PFDATA could contain a colon separate list of
| directories.  Or Bob did.  Was someone lying?

Jay, you need more sleep or less of something else.

No one said anything about PFDATA containing a colon
separated list . . . that's PFDSK.

$PFDATA$PFDIR/filepro tells filePro where the filePro
files (and their formats and programs) are located.

I've seen a lot of misunderstanding about these two
variables (in fact one of the filePro Documentation
Files had them bassackwards).  Some people leave one
or the other of them NUL and put all of the information
in the other one.

Originally, PFDATA was meant to hold the mount point of
HDs . . . / for the root filesystem, and /hd1, /hd2, /u,
/u1, or whatever for other filesystems, and PFDIR then
pointed from there to the "filepro" directory on that HD.

Whatever, PFDATA and PFDIR ar fixed in filePro's mind
when it starts up.  In-so-far as PFDISK, filePro will use
the elements of this to replace PFDATA while using PFDIR
to point to "filepro" directories where it might find
filePro Files holding key, data or index files belonging
to the filePro Files in $PFDATA$PFDIR/filepro.

Clear as mud, huh?

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).