Hi,
An other question is, that how can you tell to the platform, to limit these features, maybe non-modifiable environment variables and command line parameters can be the ways of it.
For that you need a full-blown quota and privilege system. Luckily there are plans for one. :)
As far as boxing a VM into a sub-directory, etc. UNIX (chroot) and VMS make this a breeze since
the mechanisms are builtin to the OS, it is Windows where all the work has to be done.
I'm not a UNIX guru, but I don't know an easily installable solution for the problem. I would like to run just one Apache, and would like to run Perl as an Apache module. Chroot I think is not a solution for it. Running the script as CGI or running as much Apaches as much client you have is not a solution for me and for a lot of people. PHP offer an easy way to solve this problem.
It's important here to note that when I said "platform" I meant "Parrot". (That was in there, but it's worth being clear about) That is, the platform is Parrot, not the OS parrot is running on, and Parrot is responsible for any security guarantees it makes. Now, it may make them by using facilities the OS provides (which makes the job easier) but it doesn't have to -- it can and will do it with no OS help if need be.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
