In the use case where the same pbc exists in multiple places in a filesystem (or is renamed during run, or lives on a filesystem without a good definition of "same place"), it's necessary to detect when a load is redundant.
I'm planning to require a UUID in the pbc header which would make each pbc distinguishable from every other pbc. This would have no privacy issues if it's done right, because the pbcs are identified, not the parrot installations that create them. Any problems here? Any suggestions for UUID code that's licensed appropriately for use in Parrot? -- Chip Salzenberg <[EMAIL PROTECTED]>
