To achieve that, you should modify the .htaccess file by adding the following:
AddHandler x-httpd-php5 .php
AddHandler x-httpd-php .php4

The new handling will apply to all .php scripts in the current directory and it’s sub-directories. PHP4 will looks for the .php4 extension in this case. Note that the second line is necessary, otherwise a handling conflict will occur.

From a unix environment, simply execute the following replacing username and server by the appropriate values. This will create a SOCKS proxy on port 3333 (you can of course use another port):
ssh -D 3333 -f -C -q -N username@server

Now, you just need to modify your browser preferences to use that proxy and you’re done. In Firefox, head to preferences and find the connection settings. Use manual proxy configuration, and enter in the SOCKS proxy field localhost on port 3333.

Simply install the required packages as follows:
sudo apt-get install openssl ssh

You can now access your computer from another machine using an SSH client. From another linux machine, you could access it using the following format:
ssh username@machine

SSH behind router
If you’re using a router, and would like to SSH your computer from an external network, you should configure your router to forward the SSH port (default: 22) to the computer in question. This procedure differs from a router to another; look for ‘Port Forwarding’ in the configuration menu of your device.

SSH without a password
This is extremely useful if you don’t want to type your password from the client every time you SSH, of if you are automating SSH login. The process is described on SSH Without a Password.

Now, if you want to open the screen at a specific resolution, for example 1280×1024 resolution, add the -g flag:
rdesktop -g 1280x1024 [machine]

You should try to investigate why this is happening. Still, a quick trick to fix it and can restore the missing sock is simply creating a symlink to the original one:
ln -s /var/run/mysqld/mysqld.sock /tmp/mysql.sock

Dumping is the process of putting the database content to file. It can be done using the following command:
mysqldump -u[user] -p[password] [db-name] > dump.sql
replacing where appropriate the parameters [user], [password] and [db-name]; you should not use the brackets and watch the spaces.

To restore the content of the database from a dump file, use the following command:
mysql -u[user] -p[password] [db-name] < dump.sql

Troubleshoot: Error 1044
This solves the problem when getting the following error with $mysqldump$:
Got error: 1044: Access denied when using LOCK TABLES

The message is self explanatory. You have two solutions to solve the problem. You can either modify the database LOCK privileges (not explained here) or you could add --single-transaction flag to the mysqldump command as follows:
mysqldump -u[user] -p[password] [db-name] --single-transaction > dump.sql

Do the following:

1. rm -r ~/.gconf/apps/panel
   This will remove the panel configuration, you can back it up first if you’re paranoid.
2. Log out of GNOME (shortcut CTRL + ALT + BACKSPACE)
3. Log back in and you’re done.

Quick reminder:

• tar is an archiver used to to combine multiple files into one
• gzip is a compression tool used to reduce the size of a file

Now that you finally understand the difference, here’s how the basic operations work:

• Create a tarball with the content of a directory:
  tar -cvf foo.tar foo/
• Extract the content of a tarball:
  tar -xvf foo.tar
• Compress a tarball with gzip, this will replace foo.tar with a compressed version foo.tar.gz:
  gzip foo.tar
• Extract a gzipped tarball:
  tar -xvzf foo.tar.gz