You can issue Solaris commands from within Prism.
From the menu bar - Choose the Shell selection from the Utilities menu. Prism creates a Solaris shell. The shell is independent of Prism; you can issue Solaris commands from it just as you would from any Solaris shell. The type of shell that is created depends on the setting of your SHELL environment variable.
From the command window - Issue the sh command on the command line. With no arguments, it creates a Solaris shell. If you include a Solaris command line as an argument, the command is executed, and the results are displayed in the history region.
Some Solaris commands have Prism equivalents, as described below.
By default your current working directory within Prism is the directory from which you started Prism. To change this working directory, use the cd command, just as you would in the Solaris environment. For example,
cd /sistare/bin
changes your working directory to /sistare/bin.
cd ..
changes your working directory to the parent of the current working directory. Issue cd with no arguments to change the current working directory to your login directory.
Prism interprets all relative file names with respect to the current working directory. Prism also uses the current working directory to determine which files to show in file-selection dialog boxes.
To find out what your current working directory is, issue the pwd command, just as you would in the Solaris environment.
You can set, unset, and display the settings of environment variables from within Prism, just as you do in the Solaris environment.
Use the setenv command to set an environment variable. For example,
setenv EDITOR emacs
sets your EDITOR environment variable to emacs.
Use the unsetenv command to remove the setting of an environment variable. For example,
unsetenv EDITOR
removes the setting of the EDITOR environment variable.
Use the printenv command to print the setting of an individual environment variable. For example,
printenv EDITOR
prints the current setting of the EDITOR environment variable. Or, issue printenv or setenv with no arguments to print the settings of all your environment variables.