Language Selection

English French German Italian Portuguese Spanish

Ubuntu 6.04 pre-beta (Dapper Drake)

Filed under

The development cycle of the next major release from the wildly popular Linux distribution Ubuntu started on October 20 and was given the monicker of Dapper Drake. That is a name we will all be hearing quite a bit on the road to final, scheduled for April 20, 2006, and well beyond. Let's a take a look at a recent build for the upcoming Ubuntu 6.04. I choose to call it "pre-beta."

Dapper's admirable goals include software discovery and installation, making it easier to install new software; network-wide enterprise updates for simplified centralized administration; and support for Dapper on mission-critical enterprise servers. Said of the development cycle, "we want to make sure we can deliver on the promise of a super-stable and ultra-polished Ubuntu for the masses."

In a wiki document titled "DapperGoals", it is written:

Feature Goals

  • Substantial polish and integration of the existing desktop environment is the primary desktop goal, for both Ubuntu (GNOME) and Kubuntu (KDE).

    • Dapper should come pre-configured to do the Right Thing, without asking questions, with all forms of content that the standard install is configured to handle. Double-click on a PDF, and you should see it in Evince (Ubuntu). Double click on a PNG, and you should see it in the Gnome image viewer.

    • The sound theme should be professional, and muted by default (other than startup and shutdown sounds).
    • Artwork will be an evolution of the Breezy artwork, with substantial work done to make an excellent overall visual impression on Ubuntu, Kubuntu and Edubuntu.
    • High priority will be given to specifications that require relatively little new code but improve the "smoothness" or polished feel of the final product.
  • Software discovery and installation will be a target of focused work. It should be even easier to find software that is either part of Ubuntu main, or universe/multiverse (recognising the issues of support and supportability involved), and even 3rd party software that is built and packaged for Ubuntu.

  • We will work hard to make network-wide enterprise updates easy to manage. So people who are deploying Dapper across a corporate network can ensure that they retain control over the distribution of updates to those desktops.
  • We will consider LSB and related certification standards. We have not yet determined the feasibility of aiming for compliance with such standards, but will take the decision at UBZ.
  • We will support the server administrators who want to deploy Dapper on mission-critical servers, with a flavour of kernel specifically tuned to meet their needs.

Are they on the right track? This will be my first install of Ubuntu. I've briefly looked at the livecds of Ubuntu and Kubuntu and reviewed Edubuntu livecd, but never actually done a hard drive install and spent any real length of time exploring the depths. I'm not a fan of gnome or agree with the sudo philosphy of better security, but today I take a look at what will become Ubuntu 6.04.


It all starts with a download, a burn, a boot. One is greeted by what I refer to as an "ascii-graphic" installer. It walks the user thru various steps in order to obtain an Ubuntu Linux install. The beginning stages are non-interactive while the installer does some setup and hardware detection.

My install became interactive when it failed to detect my network card(s). Instead it offered to let me go thru hardware detection again, and when it failed again it insisted I had some firewire hardware to configure. I declined to configure that as I actually have none and after looping thru this process a few times, I ctrl+alt+F2'd to a terminal and modprobe via-rhine. That helped the installer detect my network card and it proceded to set up dhcp and bring up the connection.

I was asked my hostname and sent to a hard disk partitioner. Given the choices of formatting all of either of my hard drives or manual, I chose manual. Next, I chose the partition I wanted to install upon, set up some options, and clicked yes to procede. I was asked my timezone and it was off to install the base system and copy the packages.

After a short while of installing I was asked to set up a user and it left me alone again to do some more configuring, most notably the apt installer. After the myocardial infarction that the progress bar/screen gave me when it said it was installing grub on my lilo system, I was asked for my input as to where to install it <shewee>. Skipping this step wasn't offered, but I could choose /dev/fd0.

At this point the system wants to reboot to install the software packages and it shoots a screen about level of error reporting, but doesn't give one time to read or adjust the level. Augh well, not important -> reboots.

Here is where it picks up the software installation. After it mounts all partitions it can possibly find, it asks for input concerning the X resolution desired, and continues installing and configuring our new ubuntu system. I was left scratching my head and making a mental note to google the "bicyclerepair" configuration it spent a few seconds working. As I haven't had a bicycle in about 20 years, I've since googled and found it's a framework and refactoring tool for Python. hmmmm... ok.

Now we can log-in. Foregoing the personal critique of color choice, the login is a nice tidy screen featuring a few options. In the lower right hand side is one's machine name and time of day. On the left are the options to reboot or shutdown. In the primary focal area, one can choose their language (only don't!). Choosing this option opens a nice big empty box that renders the system locked. A hard reset with all partitions mounted later, we can now choose our session. We are basically offered gnome, gnome, or gnome. I chose gnome.

The System

One is ushered into their shiny new Ubuntu desktop by an attractive nautilus splash box and relaxing startup sound. An uncluttered desktop of Gnome 2.13.1 is served up by Xorg 6.8.2 ontop of Linux-


The menus are chocked full of applications for just about any task at hand. In the accessories menu we find things such as an archive manager, file browser, dictionary and calculator. In the graphics menu are gimp, image viewer (eye of gnome), a thumbnail viewer (gThumb), and xsane (which worked out of the box here). Your game choices are not limited by their gnome/gtk dependency as 17 different applications are given ranging from solitare and black jack to mines and gnometris.

 2.0 is found in this pre-release as well as evolution for mail, firefox for browsing, gaim for instant messaging, gnomemeeting for video conferencing, X-chat for irc, and bittorrent for file sharing.


The sound menu has many different applications for listening to or ripping of music as well as burning a cd. The systems tools offered range from menu editing, system configuration, system logs, reporting bugs, to loginning in as another user. The places menu has nice links for seaching for files, browsing local files or connecting to network folders.


Under System we find Preferences and Administration. In the preferences menu we find shortcuts to all kinds of system configuration tools. One can customize their system to each his own including Assistive Technology Support. Under Administration one can configure their network connection, view disk information, add users or groups, adjust time and date, edit the menu and much much more.


There is also help available. Gnome has it's help available and Ubuntu provides specific help for using their system. One can browse these local html and man pages or be taken to the Ubuntu wiki.


And of course the piece de resistance: synaptic. What is any deb system without apt-get and front-end synaptic? Ubuntu's version worked as advertised here. Smooth, even flawless, installation of additional applications, if they were available, was experienced. I was disappointed to not find xawtv or mplayer offered in the default apt-get repository.



During my testing of this not-even-an-alpha, Ubuntu Dapper Drake seemed very stable with only a few glitches here and there. Besides the few mentioned above, trying to use totem first shot an error about not being able to use the video device and then locked the system up. Any delay in inputting your user password in the dialogue boxes presented for apps requiring root priviledges resulted in a lock up. The cd player worked the first time and then never again.

The default desktop itself was quite nice if you don't mind the color. The theme was a very nice and unobtrusive choice and ubuntu always has some nice wallpapers. The abundance of software included leaves hardly any use for synaptic.

The installer wasn't any more user friendly than anyone else's. Seems if developers, not ubuntu specifically, take away the software selection step they call it more user friendly. It worked as designed except for the network card glitch.

So, all in all, Ubuntu was found to be another nice and capable Linux distribution. I don't understand all the big hoopla surrounding it. It's nice enough, but I just can't see what everyone else does. To me there are many as nice and several nicer. But if it's your cup of tea, it doesn't look as tho Dapper Drake is going to disappoint you.

More Screenshots in the gallery.

More in Tux Machines

KNOPPIX 7.7.1 Distro Officially Released with Debian Goodies, Linux Kernel 4.7.9

Believe it or not, Klaus Knopper is still doing his thing with the KNOPPIX GNU/Linux distribution, which was just updated to version 7.7.1 to offer users the latest open source software and technologies. Read more

CentOS 6 Linux Servers Receive Important Kernel Security Patch, Update Now

We reported a couple of days ago that Johnny Hughes from the CentOS Linux team published an important kernel security advisory for users of the CentOS 7 operating system. Read more

Games for GNU/Linux

  • Why GNU/Linux ports can be less performant, a more in-depth answer
    When it comes to data handling, or rather data manipulation, different APIs can perform it in different ways. In one, you might simply be able to modify some memory and all is ok. In another, you might have to point to a copy and say "use that when you can instead and free the original then". This is not a one way is better than the other discussion - it's important only that they require different methods of handling it. Actually, OpenGL can have a lot of different methods, and knowing the "best" way for a particular scenario takes some experience to get right. When dealing with porting a game across though, there may not be a lot of options: the engine does things a certain way, so that way has to be faked if there's no exact translation. Guess what? That can affect OpenGL state, and require re-validation of an entire rendering pipeline, stalling command submission to the GPU, a.k.a less performance than the original game. It's again not really feasible to rip apart an entire game engine and redesign it just for that: take the performance hit and carry on. Note that some decisions are based around _porting_ a game. If one could design from the ground up with OpenGL, then OpenGL would likely give better performance...but it might also be more difficult to develop and test for. So there's a bit of a trade-off there, and most developers are probably going to be concerned with getting it running on Windows first, GNU/Linux second. This includes engine developers.
  • Why Linux games often perform worse than on Windows
    Drivers on Windows are tweaked rather often for specific games. You often see a "Game Ready" (or whatever term they use now) driver from Nvidia and AMD where they often state "increased performance in x game by x%". This happens for most major game releases on Windows. Nvidia and AMD have teams of people to specifically tweak the drivers for games on Windows. Looking at Nvidia specifically, in the last three months they have released six new drivers to improve performance in specific games.
  • Thoughts on 'Stellaris' with the 'Leviathans Story Pack' and latest patch, a better game that still needs work
  • Linux community has been sending their love to Feral Interactive & Aspyr Media
    This is awesome to see, people in the community have sent both Feral Interactive & Aspyr Media some little care packages full of treats. Since Aspyr Media have yet to bring us the new Civilization game, it looks like Linux users have been guilt-tripping the porters into speeding up, or just sending them into a sugar coma.
  • Feral Interactive's Linux ports may come with Vulkan sooner than we thought
  • Using Nvidia's NVENC with OBS Studio makes Linux game recording really great
    I had been meaning to try out Nvidia's NVENC for a while, but I never really bothered as I didn't think it would make such a drastic difference in recording gaming videos, but wow does it ever! I was trying to record a game recently and all other methods I tried made the game performance utterly dive, making it impossible to record it. So I asked for advice and eventually came to this way.

Leftovers: Software

  • DocKnot 1.00
    I'm a bit of a perfectionist about package documentation, and I'm also a huge fan of consistency. As I've slowly accumulated more open source software packages (alas, fewer new ones these days since I have less day-job time to work on them), I've developed a standard format for package documentation files, particularly the README in the package and the web pages I publish. I've iterated on these, tweaking them and messing with them, trying to incorporate all my accumulated wisdom about what information people need.
  • Shotwell moving along
    A new feature that was included is a contrast slider in the enhancement tool, moving on with integrating patches hanging around on Bugzilla for quite some time.
  • GObject and SVG
    GSVG is a project to provide a GObject API, using Vala. It has almost all, with some complementary, interfaces from W3C SVG 1.1 specification. GSVG is LGPL library. It will use GXml as XML engine. SVG 1.1 DOM interfaces relays on W3C DOM, then using GXml is a natural choice. SVG is XML and its DOM interfaces, requires to use Object’s properties and be able to add child DOM Elements; then, we need a new set of classes.
  • LibreOffice 5.1.6 Office Suite Released for Enterprise Deployments with 68 Fixes
    Today, October 27, 2016, we've been informed by The Document Foundation about the general availability of the sixth maintenance update to the LibreOffice 5.1 open-source and cross-platform office suite. You're reading that right, LibreOffice 5.1 got a new update not the current stable LibreOffice 5.2 branch, as The Document Foundation is known to maintain at least to versions of its popular office suite, one that is very well tested and can be used for enterprise deployments and another one that offers the latest technologies.