Impact of OpenSUSE 12.1 on Tumbleweed

My major motivation for trying Tumbleweed was to have an Arch Linux like distribution but with delta packages. Although delta rpms were only available for the packages in the 11.4 repository and not in the Tumbleweed repository, I continued to be interested in seeing how the 'rolling' model will evolve along with the other distributions of OpenSUSE.

The release of 12.1 distribution had a larger impact on Tumbleweed than I had expected. It was literally a distribution upgrade, no different from 11.4 to 12.1. Tumbleweed repository was emptied and based on 12.1 repository. All packages were upgraded. I had hoped that the Tumbleweed distribution to be very close to the 12.1 and the upgrade should have been minimal even though I had wondered how they will manage versions across repositories.

In the current upgrade, I had to change the repository to point to the current repository instead of 11.4. The current repository is now a symbolic repository so in future no change in the repository information will be needed. However, at least at present, Tumbleweed does not really appear to be a rolling distribution. It is more like the base with some updates, so, not particularly interesting. It is better to use Ubuntu with ppa's.

I will keep watching and may be Tumbleweed will evolve into an interesting alternative. At present, I continue to stick to Fedora and Arch Linux at home and Ubuntu at work.

First Experiments with Ubuntu 11.10

The upgrade to Ubuntu 11.10 went through smoothly on Lenovo S10-3 netbook. It looks very similar to 11.04. An application would normally use the full screen as expected. I tried to start a new application and couldn't. No matter where or how hard I pushed the mouse, the dash would not appear.

Finally, I remembered the 'window' key! Having found the workaround, I have not had a chance to experiment with it more as I normally use Arch Linux on the netbook and Fedora on the desktop.

At IIT, Ropar, the default desktops are Ubuntu. So, I decided that I would try to upgrade my LTS desktop to oneiric. I certainly wasn't going to upgrade in steps. The choice was between a fresh installation or an forced update and do what is not recommended - strongly.

The latter is more fun and I hoped to learn something. I changed the sources file to use the oneiric repositories. My installation was fairly simple so I did not expect any significant issues. At worst, some packages would be broken.

Unfortunately, the upgrade failed - too many errors. The last error was a fairly simple error of some conflict in a file in two packages. I made the mistake of rebooting inspite of the broken packages!

The system no longer boots - not even grub menu :(

Well, I will now have to do a fresh installation - and haven't understood what went wrong.

Fedora 15 takes too long to boot: traced to Systemd?

I filed a bug report - "System takes over 2 additional minutes to boot after updating to kernel 2.6.38.8-35".

This was in July. The problem was erratic. If I tried to trace it, it seemed to disappear. It persisted even after upgrading to 2.6.40. In fact, it seemed to be more consistent. Removing VirtualBox 'solved' the problem but not for long.

Then finally an entry in the system log messages helped!

Oct 25 15:22:28 amd avahi-daemon[1792]: Registering new address record for fe80::217:31ff:fe93:e65a on eth0.*.
Oct 25 15:27:26 amd systemd[1]: network.service operation timed out.  Terminating.

Fortunately, I had not rebooted the system and let it try to boot for over 5 minutes.


It led to the realisation that I had been running network service even though it was not needed any more when using NetworkManager.

Now for the last three days, the system has been booting fine after I disabled the network service.

I will wait a few more days before filing a bug report against systemd - just to be sure.

Facebook makes me younger!

I admit that I am not very good at using using Facebook or knowing what it is asking. However, I was somewhat amused by the status update that I had added Padre Conceicao College to my educational qualifications.

How did it happen?

I got a request that some of my Facebook friends have said that they were at the college at the same time as I. It wanted me to confirm that fact. It seemed like a trivial issue and I confirmed it.

Facebook said that this fact has been added to my profile. What! I did not state that. Oh, well. I do not take Facebook seriously so it mattered little.

So, now I have said to the world that I was a student at this college at the age of 55 when in fact my relationship with the friends was that they were in the classes I was teaching :)

User Interfaces and Familiarity

Getting used to a new interface can be hard, even if it not Gnome3 or KDE4.

I just realised it after 4 years of using my car that the petrol gauge is not linear! I haven't been driving much - less than 10,000 KM in 4 years. Even then I felt silly.

These days, I am driving to Ropar (approx 50KM from Chandigarh) thrice a week and noticed that the petrol seemed to deplete rapidly after reaching the midway point. I was thinking whether there is a problem and then I noticed for the first time that there is an icon at the mid-way point. The icon is of a petrol pump - clearly implying that it is time to fill up :)

Oh, well. Works as intended.

Rsync - What on earth did I do!

I created a new document related to a course I am teaching on my netbook. I rsync'd my netbook to the desktop. To my horror, the lecture notes I had prepared on the desktop were over-written by the version on the netbook.

Why can't software prevent me from doing something so dumb.

Well, I should have examined the implications more carefully for bi-directional rsync.

Another often used flag not included in -a is -u, which says not to overwrite newer files. If we wanted to do a Briefcase style synchronization, we need -u, and we need to do the rsync in two directions:

rsync -aHu a/* b
rsync -aHu b/* a

Arch Linux - experience with kernel 3.0

Upgrading to kernel 3.0 on Lenovo S10-3 did have a couple of issues. The first issue was that the wifi was not functioning. This was easily solved by following the instruction on Arch Wiki and blacklisting the conflicting bcma driver.

The other issue was that waking from sleep is not working any more. This is in spite of  adding 'intel_idle.max_cstate=0' to the kernel boot options. Hence, I reverted to kernel 2.6.39 until I have time to examine the problem in more detail and see if  there is a workaround.

Incidentally, I have been facing erratic behaviour with waking from sleep on Lenovo S10-3 with Ubuntu 11.4 with 2.6.38 kernel and Fedora 15 with 2.6.40(!) kernel. I thought that the reason may be that I am using x64 versions of Ubuntu and Fedora whereas on Arch Linux I have installed the i386 version.

Update: A silly mistake in Fedora 15 grub.conf file. I had typed 'state' instead of 'cstate'. Initial tests of sleep work on Fedora 15 with kernel 2.6.38 but not with 2.6.40 (presumably the same as mainline 3.0). I will have to check if the behaviour of waking from sleep on Fedora is consistent as on Arch Linux or erratic as on Ubuntu.

Update 2 -  I found that there is a bug report of the waking from sleep issue on Debian bugs list when upgrading from 2.6 to 3.0.