Running a program on the system accessed via ssh

Controlling anything remotely is always kinda exciting and fun. And when it comes to computers its even more exhilarating. So when I became aware of ssh I was excited. Tried poking fun at people in computer lab by logging into their system and closing their programs and rebooted their computer. For a command line freak like me its even more fun to be able to actually control another computer from terminal.
But if you have tried running a program which requires a GUI you would have found that it gives an error stating

Error: No Display found.

I always wondered how that could be achieved but never knew really tried to find out. Today, however I decided to find out and blimey!!  a simple internet search revealed the answer. Prefix the program with this DISPLAY=:0. So if you want to run the terminal program on a gnome system run

$ DISPLAY=:0 gnome-terminal

And BINGO !!!

Compiz Fusion screws up in Ubuntu 11.04

A new recruit, at AmiWorks, got Dell Vostro with Ubuntu 11.04 to work on. Being new to Linux he was enjoying the experience but a little while later when he had played all the pre-installed games the excitement of a new OS started diminishing. And he was now in the state of comparing Linux with Windows. He approached me asking for something exciting to do with his Linux box and I obliged.
The most fascinating thing that boggles a new Linux user is the rotating cube virtual desktop arrangement. I exclaimed "Okay, I will show you something, that will make you forget Windows forever". And installed Compiz Config Settings Manager. Since I have not tried Ubuntu, I didn't know that Unity didn't support Compiz. So it broke and left me in a fix.
Now the guy had the opportunity of mocking my statement "Something that will make me forget Windows forever .. aha". Having no previous experience with Natty I could restore the system to the way it was, only with a little help from #ubuntu IRC.
Firstly chose restore to defaults on ccsm (compiz config settings manager) and then fired

$ unity --reset 

on the terminal. This fixed the situation on that computer and should be helpful for anybody else who screws up in a similar manner.

Moral: Don't boast off about ccsm until you have yourself tried it on the new configuration.