One of the boxes I've used is a SunOS 5.10 system with 8 Quad-core CPUs and 128GB of RAM. SunOS 5.10 is the base OS for Solaris 10 and Google as always yields some good information.
Some general UNIX information for monitoring your processes is 20 Linux System Monitoring Tools. Most of the tools mentioned worked on Solaris 10 (the article is for Linux) and with some slight adjustment and review of the man pages (try “man man” on the command line if you don't know what a man page is) can provide some helpful insight.
The default shell on Linux systems. It is installed and available on almost every system I've used and was installable on the remainder. Modern with tab completion and other features; with a little bit of prep it is very user friendly. Many resources exist on the internet to help with this popular shell.
For an overview of the default shell on Atlas 3 see: http://www.kornshell.com/info/. For shell programming the korn shell is one of the most used and flexible.
* This section needs to be expanded considerably.
A shell with C like commands and syntax. Was popular in the 70's. The lack of true C versitility and functionality leave this shell lacking for anything of any order of complexity. If you use it you are on your own, good luck! See http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/ if you still wish to use this shell.
An extremely versatile but difficult to learn text editor. Vi is available on almost every UNIX system in existence. Vi improved (vim) is a more modern and updated version of vi with syntax highlighting, etc. A big thank you to Bram Moolenaar, author of Vim.
These are a Unix staple and if you do any programming in almost any language you will touch them at some point. They are heavily used in Perl and Shell programming. Python and Java both have libraries for using them.
1. To run commands from command line that have spaces use print 0, i.e.:
find ~ -type f -print0 2>/dev/null | xargs -0 grep -l Tkinter >| /tmp/tk
2. dos2unix. Occasionally on Solaris moving files either from Windows to Unix or from one folder to another causes the programs to stop running from the command line. An error such as “: bad interpreter: No such file or directory” is common. This usally means there is a problem with the end of line terminators in the file. The first thing to do is run dos2unix. This will often fix the problem. However, if dos2unix doesn't resolve the issue try:
perl -p -i -e 's/^M//' <file name here>
The ^M is achieved by typing Ctrl-V Ctrl-M. It is a tip from http://www.linuxquestions.org/questions/linux-general-1/bad-interpreter-no-such-file-or-directory-213617/ and has worked when dos2unix did not.