scOttman,sc0ttman wrote: thanks for the info... But why not just use a file called 'pinstall.sh' instead?? It would greatly increase compatibility with other tools and packages..
If you mean a file called "pinstall.sh" inside the SFS file, this could be done, but you'd have to edit the SFS file. Outside of the SFS file, it has to have an identifying name for each SFS file, otherwise it would load the first "pinstall.sh" found which might not be the one belonging to the loading SFS file.
With some SFS files, I frequently have some specific configuration profile information only for that SFS to setup before executing the program.
Regards,
s