Re: ANNOUNCE: freeWrap 6.1 released

Joe English <jenglish@flightlab.com> wrote:
> Bryan Oakley wrote:
> >joey wrote:
> >> The ones I have found are auto_execok, file, and glob. The problem is
> >> the name of the executable is now a directory so commands which would
> >> normally work for the starpack as a file now no longer work from within
> >> the starpack on the starpack itself. Does that make sense?
> >
> >Yes. I knew about that restriction. I guess it never occured to me that
> >a program would want use a filesystem command on itself. Can you not
> >simply special-case the starkit itself? That is, put a wrapper around
> >glob so that if you're globbing something that should return the
> >startkit, you append [info nameofexecutable] to the result? Likewise for
> >auto_execok and the file commands.
>
> 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. But that directory usually
> doesn't exist whereas [info nameofexecutable] always does :-)

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?

Thanks,
Joey
Received on Thu Sep 29 14:36:33 2005