Ubuntu Dapper Drake, version '6.06', was released on 1 June 2006
User Story 1: on an iBook 12" 800MHz
I installed Dapper onto my iBook a few weeks ago and have been fairly please with it. Obviously there are a number of issues of stability but that is only to be expected of a developer release. One of the most interesting additions to Dapper is NetworkManager, which simplifies configuring network settings substantialy. Unfortunately there have been a number of problems with it on my laptop - now it doesn't even recognise any network interfaces at all. However, once this all gets sorted it is going to be a big help for those using portables. I have installed and run Moodle, which works well also. --WilliamRoe
User Story 2: on a Dell Latitude C800, 384 MB RAM, 20 GB hd
The Dapper Live CD and install CD (they are one and the same now) had significant difficulty with this now aged Dell laptop's video screen. I tried a number of different options from the initial boot screen but each time I ended up with a doubled display once I got to the Gnome desktop. Surprisingly the UbuntuBreezy Live CD, version 5.10, was able to sort this laptop's hardware without difficulty. So I did the following. I did a complete clean install of Breezy. No problem, everything worked fine. Then I went in to Synaptic and changed the repositories identified in the sources.list file. Simply change breezy to dapper on each, reload the repositories data which will prompt acknowledgement that a distro upgrade is available, mark all upgrades and apply. In no time at all I had a perfectly functioning Dapper install. -- RandyMetcalfe 2006-06-30 12:04:23
User Story 3: on an IBM X41 laptop, 1GB RAM, 40 GB hd, dual boot with Windows XP
This laptop was already dual boot with Windows and UbuntuBreezy. Since it was working fine, the simplest thing was merely to change the repositories to dapper as above. Dapper is now working great. I have had no issues. -- RandyMetcalfe 2006-06-30 13:02:17
User Story 4: on a Viglen genie desktop, 1GB RAM, 250 GB hd
This had been a dual boot machine (Windows XP and UbuntuBreezy), but I was ready to move to a new solution. Since this work desktop had sufficient power and capacity, and because of some of the features of Dapper, including its easy access to and installation of Sun's JRE, I felt I could move to a virtual machine solution to my very periodic need for a Windows environment. Since this is based in an educational instituation which has Microsoft Campus Agreement there were no financial implications to wiping the current Windows deployment and moving to a Windows virtual machine instead. VM Ware http://www.vmware.com/ offer a free player these days, which is accessible in Dapper's multiverse repositories. Of course that won't make the Windows virtual machine for you - that still requires someone with the full version of VM Ware and the appropriate licences for Windows. But still, this is a useful solution to test given my particular work environment.
And how did the virgin install go on a fully wiped hard drive? Smooth -- RandyMetcalfe 2006-06-30 13:24:32
User Story 5: on an IBM T43 laptop, 1GB RAM, 80 GB hd, Windows XP
Oh tale of woe! I decided to convert my nice new Windows XP laptop to a dual-boot system to satisfy my craving to fiddle about with Linux whilst not losing my capacity to conquer inferior peoples playing Civilization 4. It all started so well. After having a look for some simple disk partitioning guidelines on the Web, I used the new Dapper Live/Install CD to divide my hard drive into sections for Ubuntu, Windows, and a big shared space for files. I then proceeded to install Ubuntu in my new ext3 partition. I restarted the computer, selecting Ubuntu from the boot menu. There seemed to be a problem picking up my wireless network connection, but otherwise everything worked. It was simple. It was brilliant. I turned my computer off and started it up into Ubuntu several times without problem. I it started up and booted into Windows without problem. But when I next shut down and started up... the computer restarted, and restarted again, and again, in a loop, without even getting so far as the boot menu. I could restart from the live CD, but that was it.
After spending a day fiddling around trying to get things working, and reinstalling Ubuntu four times, I gave up. I got one of our IT guys to remove the Grub bootloader and after that was able to boot back into my old Windows system once again, but with no Ubuntu. It seems from looking at various bug reports that my problem might be caused by the presence of Novell Zenworks on my machine, but none of the suggested fixes were applicable to my set up, and I'm loath to remove the Novell product as it was installed by my employers. I'm currently waiting for someone to come up with a bug fix that will give me the confidence to try again. -- JamesWilson 2006-06-30 16:18:42