Technology Tales

Another alpha release of Ubuntu 8.10 is out

It's probably about time that I drew attention to Ubuntu's The Fridge. While the strap line says, "News for Human Beings", it seems to be the place to find out about development releases of the said Linux distribution. Today, there's a new alpha release of Intrepid Ibex (8.10) out, and they have the details. As for me, I'll stick to updating my installed 8.10 instance using Synaptic rather than going through the whole risky process of a complete installation following a download of the CD image. Saying that, it would be nice to see the System Monitor indicating which alpha release I have. I didn't notice anything very dramatic after I did the update, apart maybe from the hiding away of boot messages at system startup and shutdown or the appearance of a button for changing display settings in the panel atop the desktop.

A first look at Ubuntu 8.10

I must admit that my curiosity got the better of me when screenshots of Ubuntu's 8.10, otherwise known as Intrepid Ibex, started to make their appearance. Since it is only at alpha2 stage, it's definitely a no-no for production systems. However, it does run surprisingly smoothly even at this stage. Yes, I have seen rough edges and the biggest of them all has made me install it onto my spare PC; there is certainly a tendency for systems to hang when you try running 8.10 in virtual machines, my preferred method for these kinds of explorations. Try it in VirtualBox and kernel panic messages ensue while you can log in on VMware Workstation only for the desktop never to load. While those could be major deficiencies for some, they have both been reported, with the former being seen by many and the latter being flagged by my own self.

Because I was using a version with the alternate installer, the usual slickness that we expect of Ubuntu installations wasn't apparent. Though I am sure that will change in time for the final release, I didn't find it too taxing to get things going with this means. Despite current changes, I expect a more familiar interface will return during later development cycles, certainly well before the final version is released. Because I was installing over the top of a previous Ubuntu installation, I didn't want to lose everything, but I needed to leave it to wipe out the previous root system partition for it to continue without freezing. Since my home directory resides on a separate partition, the transition occurred smoothly, with settings like desktop backgrounds being automatically detected without any complications. One thing that might annoy some is that all this takes manual intervention; you don't get the sort of non-destructive and seamless upgrade capability that openSUSE 11 gives.

What you get when the installation is completed is a Linux desktop that won't look too different from what we are used to using. The update introduces the New Human theme, featuring elegant chocolate-coloured elements that replace the previous default orange-brown colour scheme. They need to sort out a bug (another of my reports)  where black text is being displayed on dark backgrounds on the default display of dropdown menus in Firefox and maybe look into why changing the level of enhancements from Compiz Fusion messes up the display of the workspace switcher in the task bar, but it's fine apart from this.

Otherwise, it's a case of steady as she goes with OpenOffice 2.4, Firefox 3 and so on. That may change as time goes on, with OpenOffice 3 looming on the horizon. For some, all this continuity is all well and good, but I could foresee comments front some parts that nothing dramatic is happening, and that Ubuntu cannot afford to stand still with the advances of Fedora, openSUSE, Mandriva and so on. Saying that, I like the continuity because it doesn't mean that my apple cart is going to get overthrown now and again. Indeed, you could say that the whole Linux distribution market has matured very nicely with evolution being the order of the day and I suppose that Ubuntu needs to be seen to be evolving more than perhaps it has been doing.

In summary, it's early days for Intrepid Ibex, yet it works well even at this stage. In fact, it is running sufficiently so that I am writing this very post in a Firefox session running on the thing.  It'll be interesting to see how it goes from here and if any more pleasant surprises are visited upon us. After the "safety first" approach of Hardy Heron, I suppose that Canonical can feel a little more adventurous, so we'll see what comes. Meanwhile, Here are a few screenshots below for your perusal:

The peril of /tmp

By default, I think that Windows plants its temporary files in c:\windows\temp. On Linux or on Ubuntu at least, the equivalent area is /tmp. However, not realising that /tmp when you shut down and start your PC could cause the silly blunder that I made today. I was doing a spot of reorganisation on my spare PC when I dumped some files in /tmp from a hard drive that I had added. I was reformatting the drive as ext3 following its NTFS former life. As part of this, I was editing fstab to automatically mount the thing and a system restart ensued. I ended up losing whatever I put into /tmp, a very silly blunder. Luckily, I had the good sense not to put anything critical in there, so nothing of consequence has been lost. Nevertheless, a lesson has been learnt: Windows allows its temporary area to pick up all kinds of clutter until you clear it, while Linux clears the thing regularly. It's remarkable how Windows thinking can cause a howler when you have a lapse of concentration using a *NIX operating system, even for someone who uses the latter every day.

An introduction to Wubi

The Toshiba laptop that I acquired at the start of the year is a Windows Vista box, and it isn't something with which I want to play too roughly because the OS came pre-installed on it. I still wish to continue to see how Vista goes at close quarters, so removing it to put Ubuntu or some other Linux distribution on there wasn't ever going to be an option that I was willing to take either. Neither was the option of setting up a dual booting arrangement using disk partitioning; I have plenty of experience of doing that to set up dual booting machines over the years, and I don't need any more than what I already have. So, I was happy to leave it as a Windows box and only as a Windows box.

That situation has changed, and the cause was Canonical's decision to go for something novel when it brought out Ubuntu 8.04. The premise is as follows: a Windows style installation that pops an entry in the Windows boot menu that allows you to fire up Ubuntu without ever having to do disk partitioning or other similar rough play. For those who are less than enamoured with the Linux option, it's even easy to remove too, as easy as any other Windows program in fact. Removal of Linux is very definitely not what I'd do, and that's even without the pain and upheaval of more customary means for setting dual booting machines. In these days of virtualisation and hypervisor technology, I have my ideas as to what has been used to give us that easy way in.

Being an Ubuntu user anyway, the possibility of having Ubuntu on the laptop and the interesting opportunity that Wubi offered for getting it on there was too tempting for me to give it a miss. A small download from the Wubi website is all that is needed to set things off. You get a number of options up front, like where to put the (large) file to be used to house the Ubuntu world and how large you might want it. Setting a username and password for the thing gets included among other items. The next stage is to download the files to be used to perform the installation. Once that is completed, and it took me a few goes to get the lot (thankfully, it stores things up to the point where the downloading operation cuts out so you didn't start from scratch each time; even so, it's still annoying and could put some off), it is time to restart the computer and boot into Ubuntu to complete the set-up of the operating system itself; it is at this point that the familiar very much returns. A reboot later, and you are into a world that does its level best to fool you into thinking that Windows is another universe and never existed on that machine at all.

So, a machine that seemed destined to only ever run Windows can run Linux now as well. Wubi comes across as a neat and clever way to get a dual booting computer, and I hope to leave mine as I now have it. No feathers were ruffled on the Windows side, and I saw no sign of any destruction. That makes Ubuntu's way of doing things a much better option than other distributions that make you go down more invasive routes when creating a dual booting PC. A question remains in my mind. Could this approach take off?

Watch where you store your virtual machines when using VMware on Linux

My experience is with Ubuntu on this one, but I have found that you need to be careful as regards the file system used by the drive where you keep your virtual machines. If it is NTFS, VMware can fail to start a VM because it cannot create a virtual memory file while it presents as physical memory to a guest operating system. Use ext2 or ext3 and there should be no problem, even if that means formatting a drive to fulfil the need. That's what I did and all was well thereafter.

Running Internet Explorer on Linux

On first sight, this probably sounds daft given how good Firefox is, yet you cannot ignore those surfing the web using the ever pervasive Internet Explorer when doing some web development. Though using virtualisation is a solution to the need, it can mean that you need to set up a web server with Perl, PHP, MySQL and the like in a virtual machine, all for a little offline testing and then there's the potential for a lot of file copying too. Otherwise, you are trying to sneak things online and catch the glitches before anyone else does, never a good plan.

Therefore, having the ability to run IE to test your offline LAMP set up is a boon, and IES4Linux allows you to do what's really needed. Naturally, WINE is involved, so some flakiness may be experienced, even after the ever useful API library's reaching version 1. Otherwise, all usually runs well once you work your way through the very helpful instructions on the IES4Linux website. I did get a misplaced message about the version of WINE that I was using, and Python errors made a worrying appearance, but neither compromised the end result: a working IE6 installation on my main Ubuntu box.

IE5 and IE5.5 are also on offer if you're interested but, after looking at my visitor statistics, I think that I can discount these. IE7 and the work-in-progress IE8 make no appearance on the availability list. The absence of IE7 is not a big problem as it might appear because coding for IE6 sufficiently suffices for IE7, even now; IE8 may not be the same in this regard, but we shall see. Even so, a later browser release does mean a more secure version, and I reckon that including IE7 should be next on the project's to-do list. Saying that, what we have now is far better than nothing at all.

Killing those runaway processes that refuse to die

I must admit that there have been times when I logged off from my main Ubuntu box at home to dispatch a runaway process that I couldn't kill, and then log back in again. The standard signal being sent to the process by the very useful kill command just wasn't sending the nefarious CPU-eating nuisance the right kind of signal. Thankfully, there is a way to control the signal being sent and there is one that does what's needed:

kill -9 [ID of nuisance process]

For Linux users, there appears to be another option for terminating a process that doesn't need the ps and grep command combination: it's killall. Generally, killall terminates all processes and its own has no immunity to its quest. Hence, it's an administrator only tool with a very definite and perhaps rarely required use. The Linux variant is more useful because it also will terminate all instances of a named process at a stroke and has the same signal control as the kill command. It is used as follows:

killall -9 nuisanceprocess

I'll certainly be continuing to use both of the above; it appears that Wine needs termination like this at times and VMware Workstation lapsed into the same sort of antisocial behaviour while running a VM running a development version of Ubuntu's Intrepid Ibex (or 8.10 if you prefer). Anything that keeps you from constantly needing to restart Linux sessions on your PC has to be good.

Cleaning up Ubuntu

Uninstalling software still leaves any dependencies that came with them in place, so a quick way to get rid of any detritus is always useful. Here's a command that achieves this in a painless manner:

apt-get autoremove

Just say yes to what it suggests, to allow it on its way.

VMware Workstation in full screen mode hobbles my keyboard

Recently, I have encountered an odd situation following my recent upgrade to Ubuntu 8.04: when I use VMware Workstation to run Windows XP in full screen mode, the keyboard no longer acts as it should. For instance, the Caps Lock and Num Lock keys stop working, as does the Shift key. Logging out and back in again is the least that's needed to set things right, but there has to be a better way to resolve the problem. While I am not saying that it's limited to the scenario where I saw it happen, it's still very odd behaviour. If you have a solution, please let me know. Of course, I'll keep you posted if I find one. Meanwhile, I'll be avoiding full screen mode with VMware as much as I can.

Update 1:

I have done a spot of digging on this one since and gained the impression that there might be a conflict between VMware and the version of X.org Server that comes with Ubuntu. A restorative trick that I have seen suggested is to issue the following command in a terminal, replacing "gb" with your own locale, but I have yet to see if it works:

setxkbmap -rules xorg -layout "gb"

In any case, it looks as if it is not a permanent fix but just a way to keep working without resorting to system restarts, logging off and back on, etc.

Update 2:

I can now verify that the command quoted above works for me. Of course, it would better to find a permanent fix and even better for the behaviour never to occur at all. For now, though, any fix is better than none whatsoever.

Finding out what kernel version is running

Here's the command that does the deed for me on Ubuntu:

uname -a

Usually, I only need it to find out what header files I need for any VMware repeat installations or reconfigurations.