Very easy, just add a repository and run apt-get install postresql-9.0

Dctr Watson explains how:
Very easy, just add a repository and run apt-get install postresql-9.0

Dctr Watson explains how:
Run multiple versions of Perl from your home directory using Perlbrew!![]()
The recommended way to install perlbrew is to run these statements in your shell:
curl -LO http://xrl.us/perlbrew
chmod +x perlbrew
./perlbrew installAfter that,
perlbrewinstalls itself to~/perl5/perlbrew/bin, and you should follow the instruction on screen to setup your.bashrcor.cshrcto put it in your PATH.
I installed Ubuntu Eucalyptus cloud (#UEC) on a couple of servers at home. I was naively expecting it to be similar to VMware. Oh I was wrong.
UEC is the Eucalyptus ‘cloud’ software running on Ubuntu servers. The instances would run under the KVM or Xen hypervisors. Ubuntu’s defaulted to running KVM but isn’t restricted by it.
“Eucalyptus is a software available under GPL that helps in creating and managing a private or even a publicly accessible cloud. It provides an EC2 compatible cloud computing platform and S3 compatible cloud storage platform…” Eucalyptus Beginner’s Guide
This is how a vm works in UEC:
You publish an image that you previously installed all the software you need (or you can download such an image). There can be as many instances of this image running as the hardware supports (spread across N number of backend Node Servers).
All instances are transient. As long as an image is running, it will have a physical presence.. but when it is shutdown, the instance is removed including any work performed in the instance.
“static” storage is available via a Storage Server. After you create an image but before you start it, you have the opportunity to attach storage to the instance.
While the management tools for UEC, and therefore Amazon EC2/EM, are primitive compared to VMware, it should be able to scale much higher with far less focus on which ‘virtual machine’ goes where.
I was able to move
a VMware Server 2.0 (v7) vm to VMware ESX.. it was a *live* copy where I performed a Windows Volume Shadow copy of the vm files. Everything worked for the most part but because the database, Sybase ASE 15.0.3, was running when the shadow copy was made, we had corruption in one database. Restore from backup and all is good.
Now we need to get an updated license file from Sybase as the NIC mac address has changed.. You can *not* use the mac address from the VMware Server on ESX. grr.
Twenty hours for the volume shadow copy to complete plus another 12 hours to scp the files to the esx box (esx console access is sloooow). Keep in mind that the host VMware Server box was rebooting itself randomly so I really couldn’t leave it alone. Then 3 hours to convert/clone the vmdk files and 2 hours to correct the database… I’m tired.
It turned out to be an issue with allocating 3.75GB to a VM that was causing the rebooting. Dropping it to 2 GB resolved the rebooting… who knew? Nothing in Google and VMware Support wasn’t able to find anything on their side.
I’ve been trying to get VMware ESXi 4 on my old MSI MS-7388 motherboard for a long time. No matter what I tried, neither the SATA controller on the motherboard or the add on SATA controller would be recognized.
At this point VMware ESXi 4.0 will be installed but it won’t start when you reboot. This is because VMware won’t load the AHCI driver by default. So… we will have to tell it to load it automatically. You will need a Linux Live CD such as Ubuntu.
You should have a fully working VMware ESXi server installed and ready for you to setup virtual machines!