If all your systems NFS mount a common directory and that directory is
on everyone's PATH, one engine placed there will do the trick.
Otherwise, you'll need to put an engine on each machine that the
students use.
Be sure to also put mctools or mcmini with the engine so that the
icons, cursors, and ask/answer dialog boxes will be available.
> What's the recommended way to distribute such stacks? I assume I uuencode
> them and mail them. Is there a better way I don't know about?
Do the students need write permission for the stack? If not, just put
the stack with the engine, and have the students run the program by
typing the stack name into their terminal/shell window.
If they *do* need to be able to save the stack (e.g., to save status
information), then they'll each need to make a copy. You could just
put the stack where the engine is and then tell them to copy it into
their directories before running it.
Or, you could get fancy and have the command the students run actually
be a shell script that checks to see if they've made a copy of the
stack yet, and if not copies it for them (suggestion: name it
$HOME/.stackname so they won't accidentally delete it). The shell
script could then run $HOME/.stackname. This method could also be
expanded to handle multiple OS versions and architectures. By running
"uname" in the shell script, an engine for that particular
architecture could be run with the student's copy of the stack as an
argument (e.g,, HP9K700 $HOME/.stackname).
Scott
> Steve
-- *********************************************************************** * Scott Raney 303-447-3936 Remember: the better you look, * * raney@metacard.com the more you'll see -- Lidia * ***********************************************************************