Weblogs for jcdr
aptitude -r install linux-headers-2.6-$(uname -r|sed 's,[^-]*-[^-]*-,,') fglrx-control fglrx-driver apt-get update apt-get upgrade apt-get install fglrx*Now install some general packages.
apt-get install locales-all apt-get install mysql-common apt-get install lsb-core apt-get install libfontconfig1GoogleEarth is a i386 executable and set of libraires, even into the amd64 package of it. Since wheezy is multiarch, add the i386 parts.
dpkg --add-architecture i386 sed -i 's/deb\ /deb\ [arch=amd64,i386]\ /g' /etc/apt/sources.list apt-get update apt-get upgradeNow this will install a lot of i386 libraries. Probably that not all of them are required, but sorting them is time consuming.
apt-get install ia32-libs-gtk apt-get install libc6-dev:i386 apt-get install libc6-dev:i386 apt-get install libc6-dev:i386 apt-get install libgmp10:i386 apt-get install libgomp1:i386 apt-get install libtm1:i386 apt-get install libitm1:i386 apt-get install libmpc2:i386 apt-get install libncurses5:i386 apt-get install libquadmath0:i386 apt-get install libreadline6:i386 apt-get install linux-libc-dev:i386 apt-get install libpq5:i386 apt-get install libmysqlclient18:i386The tricky part is to get the right libGL.so.1 The procedure must be adapted if you uses an other GPU.
apt-get install libgl1-fglrx-glx:i386Now amd64 GoogleEarth should be installable.
wget http://dl.google.com/dl/earth/client/current/google-earth-stable_current_amd64.deb dpkg -i google-earth-stable_current_amd64.debIt will not be added into the Gnome3 menu. So start it manually.
1) In case your server is destroyed, you wants the latest backup and tend to backup very often;
2) In case your server is corrupted, you wants to recover the latest know good state and this is maybe not the last backup, mainly because you discover the problem while reading the backup log!
To solve this problem I use the batch option of rsync to create a "double folder" backup.
The first folder is a keep up to date by making a rsync very often. At each rsync with the first folder I also create an batch file using the "--write-batch" option of rsync.
The second folder is keep up to date only after I have review the log of the backups into the first folder. If nothing is suspect, then I use the batch files to make the second folder the same as the first one. To verify that this is the case, I make a "nothing" rsync with the "-n" option between the two folders. The result must be no transfert at all.
Of cource this methode use two times the disk space, but disk are cheap this day, far more than the time lost in case of a filesystem problem into a production server... This make also possible to automaticaly backup all the time the server and review the log when you have time to do so. In case something happens, you can restors the latest good state into the second folder by using the rsync batch files.
I also use the "--bwlimit" option to let the backup running all the times without disturbs normal operations.