Using rsync over ssh simple command

arguments used:

-a, –archive
This is equivalent to -rlptgoD. It is a quick way of saying you want recursion and want to preserve almost everything (with -H being a notable omission). The only exception to the above equivalence is when –files-from is specified, in which case -r is not implied.
-v, –verbose
This option increases the amount of information you are given during the transfer. By default, rsync works silently. A single -v will give you information about what files are being transferred and a brief summary at the end. Two -v flags will give you information on what files are being skipped and slightly more information at the end. More than two -v flags should only be used if you are debugging rsync.
Note that the names of the transferred files that are output are done using a default –out-format of “%n%L”, which tells you just the name of the file and, if the item is a link, where it points. At the single -v level of verbosity, this does not mention when a file gets its attributes changed. If you ask for an itemized list of changed attributes (either –itemize-changes or adding “%i” to the –out-format setting), the output (on the client) increases to mention all items that are changed in any way. See the –out-format option for more details.
-z, –compress
With this option, rsync compresses the file data as it is sent to the destination machine, which reduces the amount of data being transmitted — something that is useful over a slow connection.
Note that this option typically achieves better compression ratios than can be achieved by using a compressing remote shell or a compressing transport because it takes advantage of the implicit information in the matching data blocks that are not explicitly sent over the connection.
Note that -a does not preserve hardlinks, because finding multiply-linked files is expensive. You must separately specify -H.
-e, –rsh=COMMAND
This option allows you to choose an alternative remote shell program to use for communication between the local and remote copies of rsync. Typically, rsync is configured to use ssh by default, but you may prefer to use rsh on a local network.

Installing proprietary Nvidia drivers on Ubuntu Feisty Fawn

After problems on multiple machines I finally got nvidia binary drivers to work. I kept getting an error that the kernel module did not match the driver version and vice versa. Finally figured it out by searching on the net here’s my findings.

This procedure might work on other versions of Ubuntu but I don’t have those to test.

The instructions that nvidia gives with it’s binary are as generic as can be. This is a major problem for anyone who has installed the restricted drivers that are shipped with Ubuntu. If yer like me I always want the latest video drivers and you may run into some problems with that.

all the commands we will use will require root access we’ll have to use sudo. To make it easier we’ll issue sudo -s so we don’t have to use sudo in front of every command.

We first have to make sure we have the development packages with the linux headers and xorg dev installed.

Make sure we do not have any old drivers installed.

There are some files that might be left behind that will need removing
rm /etc/init.d/nvidia-glx
rm /etc/init.d/nvidia-kernel

Additionally, delete the following file if it exists:

now just install the new drivers

Follow the instructions and everything should be good.

Installing Ubuntu Studio theme on existing Ubuntu Feisty installation

Couldn’t be simpler