- If a lab or school environment has multiple OSs, and a need to SSH (telnet/ftp) elsewhere - one would only have to write instructions once.

- People who need ssh to a host, who are not comfortable with a command line, or are used to PuTTY.

These might be service desk staff who have instructions like 'ssh to host frumpty, type restart-app [enter]'

Our service desk has instructions like that, but they all use Windows. So, PuTTY. And if they use Linux .. PuTTY. It's easier.

In actuality, they call the 3rd level support and ask them to do that. And, really, we're pushing that stuff to the Enterprise scheduler so all they _really_ have to do is login to _that_ and request job task 'Restart_FOO_App' and it's done for them.

Which, in the long run, doesn't teach them how to do anything but push buttons. And is probably bad for their further development in IT. But I digress.

I don't get how one can be using a 'unix-y' computer and not be familiar with the command line. But I understand there are people out there like that.