Re: ANNOUNCE: freeWrap 6.1 released

Joe English <jenglish@flightlab.com> wrote:
>> What I usually do is to mount the starkit's VFS at someplace
>> like "/kit", instead of at [info nameofexecutable].
>>
>> Of course this causes similar problems if there's a directory
>> named "/kit" in the real filesystem.

Even better is to mount onto a mountpoint prefix that can't be in
the native filesystem. Something like "magicPrefix:/kit".

In article <11ib4p23jsjtsad@corp.supernews.com>, joey@swri.edu wrote:
> This is interesting. Do you do this when you are building the starkit or
> is this something you do within your code? Can you give me a simple
> example/walkthrough?
>
> Couldn't the starpack do this itself?

It's more the place of each Tcl_Filesystem to do this sort of thing
for itself. This is what [::trofs::mount] does, for example, generating
mount points of the form "trofs://<integer>/" to produce a unique
path prefix that doesn't conflict with anything.

-- 
| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@nist.gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|