ignoring a and b drives

[Jay R. Ashworth]

On Thu, Apr 29, 2004 at 01:41:14PM -0400, Bob Stockler wrote:
> | > 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.

Which means that if you have multiple PFDIR's under PFDSK, filePro
directories in those PFDIR's with identical names will be treated as
merged.

But, does it also merge the lists of filePro directories from all of
the located directories, presenting them all as one list? More
importantly, what if you have multiple PFDIR's in one PFDSK with the
same name but *different* data (and complete complements of files)?

Will they collide?  Loudly?  When you try to use them, or at scan time?

Enquiring minds want to know.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson