Although this is a widely debated topic I believe that a website, that is completely W3C compliant, will have better rankings in Google and other search engines. Its a logical consequence of clean code being easily read, analyzed, and interpreted. Basically your time and effort spent will be seen in how well the search engines index your website.
Ubuntu Gutsy does not use the same package name that was used in Feisty. In Feisty the NVIDIA driver was installed with:
sudo apt-get install nvidia-glx
In Gutsy the driver is installed with:
sudo apt-get install nvidia-glx-new
You can also use the restricted driver manager, which most likely recognizes your NVIDIA hardware 
Just after the release of Wordpress 2.3 the team is quickly releasing a variety of bug fixes. The speed in which this team operates is refreshing. They keep the software up to date, which significantly increases the stability of a website in a continuing effort to fight spam, and hackers.
The network manager applet, in Ubuntu Gutsy, provides a save feature that will automatically unlock your wireless keyring without the need for a manually typed password. This is a much welcomed feature, whereas in the past to unlock the wireless keyring required manual input.
I’ve experience problems backing up my web server, via scp, over my wireless connection. To resolve this I simply connected my computer via ethernet, rather than wireless. It seems that the wireless was causing the scp to stall whereas via a direct ethernet connection everything goes smoothly.
I highly recommend installing the Feisty VirtualBox package even if your are using the new Ubuntu Gutsy. First off, by default the USB host bridge is disabled in the Gusty compilation, and when you enable it manually the sound bridge fails to work properly.
I have successfully install the Feisty compilation of VirtualBox on my Gutsy desktop without any problems. This successfully resolved the USB and sound issues. Everything simply works fine.
By default the USB Host system, when installed on Ubuntu Gutsy Gibbon, is disable. To enable it is extremely simple. You can do it manually with “nano” or “gedit”. Open the following file:
sudo nano /etc/init.d/mountdevsubfs.sh
or:
sudo gedit /etc/init.d/mountdevsubfs.sh
In this configuration file there is the following section:
—————————————————————————-
#
# Magic to make /proc/bus/usb work
#
#mkdir -p /dev/bus/usb/.usbfs
#domount usbfs “” /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmo$
#ln -s .usbfs/devices /dev/bus/usb/devices
#mount –rbind /dev/bus/usb /proc/bus/usb
—————————————————————————————
To enable USB support simple remove the “#” sign in from the the bottom 4 lines so that the section looks like this:
—————————————————————————————
#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs “” /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmo$
ln -s .usbfs/devices /dev/bus/usb/devices
mount –rbind /dev/bus/usb /proc/bus/usb
————————————————————————————
Don’t forget to add the following line in your /etc/fstab configuration file (this is required to successfully mount USB devices in your VirtualBox guest OS):
usbfs /proc/bus/usb usbfs devgid=1001,devmode=664 0 0
