My buddy Dan says they rock, and well, that’s good enough for me.   I’ll post my review as soon as I’m qualified.

UPDATE #2 – 3/5/10, I have them in hand, or rather, on head!  I’m still getting used to them, but will post a review after the end of a solid week.

The error was “Warning: Attempt to assign property of non-object in /path/to/wp-content/link-template.php on line 999″

The offending code looked like this:

if ( empty($post->post_title)  )
$post->post_title = $previous ? __('Previous Post') : __('Next Post');

Even though the theme the site is using didn’t have a custom Image Attachment Template (image.php), the default theme does, so it led me to believe the issue lied with the core files.  Essentially, it seems as though the post object wasn’t being set, and since I haven’t yet had the time to delve into a more proper method for resolving the error, I simply changed the if conditions to the following.

if ( empty($post->post_title) && !is_attachment() )
$post->post_title = $previous ? __('Previous Post') : __('Next Post');

That cleared the error so at least I can get on with my life, and look into the real source of the problem when some free time shakes loose, preferrably before the next Wordpress Upgrade boils the error back to the surface.

Install Ubuntu

Download Ubuntu.    By default, the button downloads the 32-bit version.  If you need 64-bit, or a version other than the one listed, click on the Alternative download options link to expose more options.  When it’s done, you should have an disc image (.ISO) of the installation media on your hard drive.   If you are installing on a blank computer rather than a virtual machine (VM), you will want to burn that .ISO to a CD.  In Windows 7 it’s part of the native functionality, but explaining how to do that is outside the scope of this article.

Next we need to insert the media into our VM so it is available for installation.  The easiest way to accomplish that on a brand new VM is just to go ahead and start it.  You can do this by double-clicking the name of the VM in the main VirtualBox window.  This will prompt you with the First Run wizard.  Click next to pass the welcome screen and you will arrive at the Select Installation Media screen.

CD/DVD-ROM Device should be selected by default.  If not, make it so.  Under Media Source, click on the folder icon to the right of the drop-down.  This will launch the Virtual Media Manager with the CD/DVD Images tab selected.

Click on the Add icon and browse to, then select, the Ubuntu .ISO you previously downloaded.  This will close the Virtual Media Manager and return you to the First Run wizards Select Installation Media screen.  Note the Media Source.

Clicking Next will take you to a summary page.  Click Finish to begin booting the VM with the selected installation media.  The Ubuntu install should begin almost immediately.

Use your arrow keys to select your language, then hit enter.  At the resulting menu, select Install Ubuntu.  This will load a GUI installer for Ubuntu.

I have to tell you, the Ubuntu installation is about as easy as OS installations can get. Select your Language, timezone, keyboard preferences, partitioning scheme, enter your user information, and let ‘er rip. For me, the timezone and user information screen were the only two I needed to provide meaningful input for, the rest were good by default.

When it’s time to restart the machine you will prompted to remove the installation media. You can do this easily enough from the VirtualBox menu at the top of the VM window; Devices => CD/DVD Devices => Unmount CD/DVD Device. At the point, you can safely reboot by pressing the Enter key.

Once the VM comes back up, and you’ve logged in to your new Ubuntu installation for the very first time, the first thing you will want to do is install any update that has been published for your version. Do this through the GUI by navigating the System menu at the top left of your Ubuntu interface (System => Administration => Update Manager), or through the command line by bringing up a terminal window (Applications => Accessories => Terminal) and entering the following commands:

The dollar sign is not part of the command but is displayed to indicate the start of a new line which will be helpful when my examples start wrapping.

$ sudo aptitude update
$ sudo aptitude upgrade

As soon as that is finished, you might have/want to reboot the virtual machine.

$ sudo shutdown now -r

Our next step is installing the VirtualBox Guest Additions which are a set of tools designed to make interacting with your new VM a whole lot easier. Using the VirtualBox menu, select Devices => Install Guest Additions… or simple press your Host key and the D key together (Right CTRL + D by default). This will mount the Guest Additions CD and probably prompt you with a worthless auto-play window. Go ahead and cancel out of that, and return to your terminal window.

For 32-bit systems:
$ sudo /media/cdrom/VBoxLinuxAdditions-x86.run

For 64-bit systems:
$ sudo /media/cdrom/VBoxLinuxAdditions-amd64.run

Time for another reboot.

$ sudo shutdown now -r

Once it is back up, your are ready to continue on to the next step. However, if you are thinking you might want to share folder between your Host machine and your VM, it might behoove you to take a peek at this article I wrote on folder sharing. Otherwise, continue on to Step 3: MySQL, PHP, REE, and nginx via source through Passenger!

While much of this is specific to my particular requirements, this would be a good starting point for anyone looking to get their feet wet with PHP and/or RoR application development.  It would also be a good starting point for people interested in familiarizing or re-acquainting themselves with Linux, as Ubuntu is about as newb-friendly as Linux distributions get.

I should also note that even though I’m installing this as a virtual machine, it would work equally well on a real machine without the use of VirtualBox.  If you are going that route, or you are familiar with creating new virtual machines, then skip the first step altogether and go on to part 2.

Create the Virtual Machine

Install the latest release of VirtualBox for your existing platform.  The latest version at time of writing was 3.1.2.

Once installed, launch VirtualBox. From the Machine menu, select New (or press CTRL+N) to start the  Create New Virtual Machine wizard.  Click Next to continue past the welcome screen to the Name and OS Type selection screen.

Enter a descriptive name (like UbuntuDev) in the text box provided, and choose Linux from the Operating System drop-down.  After selecting Linux, the drop-down for Version automatically changed to Ubuntu on my version of VirtualBox.  If you are running a 64-bit host operating system with an architecture that supports VT-x or AMD-V virtualization technologies, then you can change the Version to Ubuntu (64 bit).  If what I just said made you dizzy, you aren’t sure how to check, or you might be exporting the VM for use on a computer you are unsure of, then leave the Version as Ubuntu.  There is no significant difference for our purposes, but make a note of which you selected so that you know whether to be downloading 32-bit or 64-bit binaries as we go on.   Click Next to continue to the Memory screen.

Select the amount of memory (RAM) you’d like to dedicate to the Ubuntu VM.  A good rule of thumb is to assign less than half of your computer’s physical RAM to your VM, but you should never need more than 2GB (2048MB) for this sort of appliance.  In fact, 1GB (1024mb) should be more than enough.  Also, keep in mind that this RAM is only used while the VM is running, so it’s not like you have to be overly stingy either.  Click Next to continue to the Virtual Hard Disk screen.

The Virtual Hard Disk screen is cake, assuming that Boot Hard Disk (Primary Master) is checked, and Create new hard disk is selected, you can click Next to spawn the New Virtual Disk wizard screen.  At the Welcome screen, click Next to continue to the Hard Disk Storage Type selection.

Another easy one, choose Dynamically expanding storage, and click Next to continue on to the Disk Location and Size screen.

The Location field should be auto-populated with a variation of the name you chose for this VM, but feel free to change it if you like.  The Size warrants some consideration.  First, an explanation; virtual disks are represented individually as single large files on your hard drive.  Had we chose Fixed-size storage on the previous screen, then whatever value we enter here would determine the size of the corresponding file.  However, since we chose Dynamically expanding storage, the size selected here only represents the largest possible size the virtual drive could consume, but in reality the file stored on our physical hard drive will be much smaller.  In this specific case, it will be less than 5GB after we’ve installed everything.  In addition, running out of space is kind of a pain to rectify, so we definitely don’t want to be stingy.  Mine defaulted to 8.00 GB, and even though I know that will be enough room for this VM’s intended purpose, I doubled it to be safe. Tripling it works too, or even quadrupling it since it is very unlikely that this VM will ever need that much space, and it will likely sit below 10gb for the duration of it’s lifespan.  Once you’ve selected a size, click Next to see the virtual disk summary screen.  If everything looks right, Finish to return to the virtual machine summary page.

Review, and when ready, click Finish there too.

Need a break?  Take one, otherwise you can continue on to Part 2 – Installing Ubuntu.

At time of writing, Overstock.com had the best price.  (89.99USD for the red ones)

Here is a Shot of Brooke’s hand and a green one!

Either way, now you want to swap files between the two of them.

The first thing you have to do, in both cases, is install the VirtualBox Guest Additions from inside your new virtual machine.  You install these from an .ISO that is installed with the VirtualBox application.  Basically you have to mount that ISO as a CD/DVD.  Thankfully, VirtualBox takes a little of the confusion out of  the process by providing you with a shortcut in the Devices Menu on your already running virtual machine. The keyboard shortcut is Host+D (Right CTRL + D by default).

Installing the VirtualBox Guest Additions on Linux (Ubuntu)

After ignoring the useless (in my case) auto-run prompt, I opened up a terminal window (Applications -> Accessories -> Terminal).  I changed directories to where the CD was mounted (/media/cdrom), and ran ls to see the contents of the directory.  After identifying the appropriate version your virtual environment, go ahead an run it as root (or use sudo if available).  On 64bit Ubuntu, it looks just like this (don’t type the dollar sign, it’s used to illustrate the beginning of the command):

$ cd /media/cdrom
$ sudo ./VBoxLinuxAdditions-amd64.run

The sudo command temporarily elevates your privileges so you can run the installer, and it will ask you to re-enter your password, so you know.

Get used to this process.  Every time you update the kernel you are going to want to re-install the guest additions.  Also, whenever you update the VirtualBox application itself, it’s a good idea to re-install them as well.

Installing VirtualBox Guest Additions on Windows

…is easy as pie.  Shortly after you mount the guest additions .ISO, an auto-run prompt will likely appear and you can just follow the prompts to run the installer.  If it doesn’t autoplay, browse the computer to the CD-ROM drive and double-click on VBoxWindowsAdditions.exe.  That should sort out the appropriate version for your current operating system.  If you are unsure about individual components, just say yes to everything.  No harm, no foul.

Again, in case you missed it above, it is possible that future windows updates could break the guest additions, so if the guest machine acts goofy after a windows update just reinstall them.   Also, plan on re-installing the guest additions everytime you update the main VirtualBox application on your host machine.   It’s painless, so quit whining.

Now that you have the guest additions installed, lets practice sharing!

Sharing Files from a Windows Host to a Linux Guest

Zhiqi Tao posted on this topic, but let me attempt a little more detail.  For this example we are going to assume you have a local directory called “C:\Downloads” that you want your Linux virtual machine to access.

On your still running virtual machine, go to the “Devices” menu and select “Shared Folders…”.   From there you will be prompted with a “Shared Folders” window, and in that window you should see a blue folder with a green plus sign in the upper right.  Click on it or press the Insert key to open an “Add Share” window.  Use the drop-down for the “Folder Path” and select “Other” to browse to the directory you intend to share, or you can simply type it in.  If you browsed to the directory, then it will auto-populate the “Name” field otherwise you will have to type that in as well.  The name field is very important here, and you will want to pay special attention to case.  Since we want this share to be available every time we start the virtual machine, and we want to be able to write to it from either system, leave “Read-only” unchecked, but make sure you check “Make Permanent”.  See the example below:

VirtualBox - Add Share Window (Windows Host)

Click “OK” to add the share and return to the “Shared Folders” window.  Under “Machine Folders” you should now see an entry with the name and path you specified above, along with Full Access. Click okay to return to the virtual machine. We are going to navigate to your home folder and create a miniature directory structure to support this initial share as well as any future shares you decide to make. Then, we are going to add a mount command to /etc/fstab and to /etc/rc.local so that the share is automatically made available every time you start the virtual machine. Play along at home and remember, Linux is case sensitive!

$ cd ~
$ mkdir Shared
$ mkdir Shared/Downloads

You are going to need to know the full path to the new Downloads directory.  It should be “/home/<USERNAME>/Shared/Downloads” where <USERNAME> is the login you created when you installed the system.  To be sure, you can enter the following commands:

$ cd Shared/Downloads
$ pwd

Make note of the output of the pwd command (which stands for  present working directory), and don’t forget about case sensitivity (you tired of me saying that yet?).  Let’s continue.

$ sudo nano /etc/fstab

Add the following line below the existing entries using the space or tab key between elements. Remember to replace <USERNAME> with your login name, and if you have been using different directories then change those as well.   It’s long, but please remember it should go on a single line!

Downloads /home/<USERNAME>/Shared/Downloads vboxsf rw,user,noauto,exec,utf8 0 0

The first element is the name of the share, and it must be an exact match for the “Name” in the list of “Shared Folders” (see the “Folder Name” in the “Add Share” example window above).  Hit CTRL+O  then Enter to write the file, then CTRL+X to exit nano.  Now we have to edit another file in /etc/, but before we do that, we need to do some self-examination.

$ id

Make note of the uid and gid values, because we are going to need them.  Mine were both 1000, and yours may very well be 1000 too.

$ sudo nano /etc/rc.local

Add the following line directly above the line that reads “exit 0″.  Feel free to copy and paste, but remember to change your uid and gid values in addition to swapping out <USERNAME> with your actual login!

mount -t vboxsf -o uid=1000,gid=1000,dmode=755,fmode=644 Downloads /home/<USERNAME>/Shared/Downloads

Again, Hit CTRL+O  then Enter to write the file, then CTRL+X to exit nano. Reboot the machine with the following:

$ sudo shutdown now -r
or
$ sudo reboot

When the machine comes back up, /home/<USERNAME>/Shared/Downloads on your guest will be the same as C:\Downloads on your host machine, and should be completely writable from either direction. Voila!

Sharing Files from a Linux Host to a Windows Guest

This is a much simpler process in comparison.  First, you select “Shared Folders…” from the “Devices” menu, then press the insert key or click the folder with the green plus sign in the resulting “Shared Folders” window to bring up the “Add Share” dialogue.   Use the “Folder Name” drop-down to select “Other” and browse to the folder you’d like to share.

Make note of the Folder Name that is auto-filled, or change it to something of your liking.  Keep it simple, and one word.  Then make sure “Read Only” is not checked, but check “Make Permanent”.  See the example in the section above.

Then, in your Windows Host, open up explorer and from the menu bar choose “Tools -> Map Network Drive”.  Choose a drive letter from the drop down, and for the folder type

\\vboxsvr\<FolderNameFromAddShareDialogue>

Obviously you want to replace <FolderNameFromAddShareDialogue> with the actual folder name from the add share dialogue.   In our previous example, it was “Downloads”.

Make sure you check “Reconnect at logon” and click on the “Finish” button.  There you go, you are all set, easy peasy.  And really, this process works no matter what kind of host you are working with.  Windows is just easy that way.

Hopefully you find this useful!

VirtualBox solves this problem for me(s) elegantly.  My Desktop is a 64bit Windows 7 machine with a healthy 8gb of ram and a roomy hard drive.   This is my primary machine for both work and play.  My secondary PC is a Laptop running 64bit Linux (Ubuntu), with 3gb of ram and a 500gb drive.  It’s feasible that I could use each machine dependent on what technology I needed at the time, but that plan is better on paper than it is in practice.

For one, not only would I hate to run every single piece of Microsoft-dependent software I could possibly need on my daily-use PC, some of them are just downright incompatible with each other.  Even if they did play nice together, the whole of it would represent a serious deterioration in available local resources which is not so good for my happiness.  Besides, I’ve never managed to shake my operating system re-installation habit that has become an almost Pavlovian response to sluggish Windows computing even though, admittedly, Microsoft OSes have gotten a lot better than they once were.  Regardless, the rigorous demand on local resources and my compulsion for total drive wipes combined with what would be a delicate and time-consuming installation process is, quite frankly, a recipe for disaster.   The bare truth of it all is, I need more than one Windows environment.  Unfortunately, I need more than one Linux environment as well.  I’m not so proud that I can’t admit being neck deep in an open-source learning curve.  I’m still experimenting and I fully expect to engage in some catastrophic mistake-making.  I need an experimental environment, a stable development one, and a working production one as well.

Thanks to virtualization, I can satisfy all these demands on a single computer.  The only hurdle is storage capacity, and current hard drive sizes make that mostly moot.  With 8gb of RAM, I can even run several of these environments concurrently.

For example, I have several Windows-based Virtual Appliances (or machines).  One is a functional backup of my previous web server running 32bit Windows 2003/SQL2000/Cold Fusion, another is a 64bit Windows 2008 R2 MOSS 2007 development environment, and last one is a 32bit Windows Vista general .NET development platform.  I’ll probably have a 4th one once MOSS 2010 ships.  As it stands right now, I’m using the old 2003 server as a staging area for .NET apps I write on from the Vista machine, and it is not uncommon for both of those to be running at the same time.

As far as Linux goes, I have 2 virtual appliances.  The first is a replica of my current co-located web server powered by Ubuntu 8.04 LTS.  It serves the dual purpose being both a living back-up of my production environment as well as proving ground for new development.  My second appliance is an Ubuntu 9.10 desktop machine that is in the process of becoming my PHP, Ruby, and Python development environment.  Both of those run simultaneously nearly 100% of the time.  The kicker is, I still have enough free resources to take a game-break now and then, and I’m not talking about solitaire.

It gets better.  Not only is VirtualBox free, it is also cross platform.  That means that I can export my virtual appliances from either my Windows Desktop or my Linux Laptop and import them to the other.  If I need to take my Windows show on the road, I simply import the appropriate appliance to my Laptop, and off I go.

Truthfully though, VirtualBox isn’t the only application that can do all that.  I think the more recent VMWare Player is quite capable of doing that much.  The one thing I love about VirtualBox though, is its “Seamless Mode”.  Seamless mode is kind of hard to explain, but essentially it is a way of running a virtual appliance so that it feels as though you are running two operating systems at once.  It simply adds a new taskbar or set of taskbars to your normal operating system interface.  This is a fantastic way to run two distinct graphical environments.  Whether I am are doing cross-platform work, client-server development, or just looking to experience a new OS from the comfort and safety of familiar ground, VirtualBox’s Seamless Mode is pure awesomeness.

I think a couple screenshots might be in order, to really drive it home.  In both examples, we have a 64bit Ubuntu 9.10 virtual appliance running on a Windows 7 Host.  The first shot is the standard mode, with Ubuntu running in it’s own window.  The second is Ubuntu running in Seamless Mode right over the top of the Windows 7 interface.  Click each thumbnail for a full size image (1920×1080 PNG > 1mb).

VirtualBox - Ubuntu on W7 - Standard Mode

VirtualBox - Ubuntu on W7 - Seemless Mode

How cool is that?  If you didn’t see anything nifty, look closer.  In the second image, you will notice the Ubuntu (Gnome) menu bar extended across the entire screen, with the Ubuntu task bar sitting comfortably on top of the Windows 7 taskbar at the bottom.  The fully accessible Windows Desktop peeks out from between them.

It was a total “Wow” moment for me the first time I experienced it and I’ve been hooked ever since.

Now, VirtualBox isn’t exactly perfect, but the development of this application is very active and it seems to get better with each release, and they are definitely frequent.  Seamless Mode has it’s own limitations too.  For example, the Guest OS (the virtual appliance machine) doesn’t span across multiple monitors, or at least it didn’t the last time I tried.  Also, you have to get used to how window focus works, meaning that when you click on a guest OS window, all visible elements of the guest OS butt in front of the host OS windows, though of course, the reverse is not true.  Then in order to access the desktop of the guest OS, you have to rely on browsing tools.  All are mainly usability concerns that you quickly acclimatize too.  Still though, even with the occasional rough spots, VirtualBox is a shining example of greatness in free (and largely Open Source) software.

You can download VirtualBox here – http://www.virtualbox.org/wiki/Downloads

The place is going to change radically so don’t get used to anything just yet.   This will be one of my little digital playgrounds, specifically a place for me to  flex my web-muscles against an otherwise stock Wordpress installation.  It should be fun, but if I were you I would check to make sure the chair is still there before you sit down.  You wouldn’t want the whole internet laughing at you because you fell on your heiney.