Demise of ArchDelta?

I have been regularly using the archdelta repository to keep my system current. A couple of months ago, the repository stopped providing updates. The arch linux discussion forum provided the answer. Sabooky was no longer using delta packages and had stopped maintaining the site.

It is disappointing as I had hoped that the experiment would become a part of the core repositories as in the case of Fedora and Suse.

This, though, provides the incentive and motivation for trying out openSUSE's Tumbleweed rolling distribution. I tried updating the Smeegol installation using the Portal:Tumbleweed advice. However, the Smeegol desktop does not appear to be a part of the Tumbleweed environment. So, only the kernel and a few packages were replaced by the higher versions.

I will start with a 11.4 livecd and then add the Tumbleweed repositories and see how it works out.

Rolling Distributions

It appears that Suse will have an option of a rolling distribution even if Ubuntu is not yet introducing a rolling distributions. For several years I have felt that this is inevitable (I still agree with the ideas in that article but wish I could have expressed them better).

A feature I miss in Arch Linux is the option to easily and quickly rollback the last set of updates in case some application or system malfunctions.

Experimenting with Lenovo S10-3 - Smeegol

I downloaded the x64 version of the iso file. It worked without a hitch and I could install the Suse's version of MeeGo on the S10-3. Unlike the 'official' MeeGo, this version has the full Suse repository available and applications like OpenOffice are already installed.

It uses gdm instead of directly using uxlaunch. The X server in this case is owned by root and not the user as in the case of MeeGo. However, this also implies that it is multiuser unlike MeeGo at present.

It is an attractive and a nice alternative to the Ubuntu Netbook and the KDE netbook workspace.

The wifi issue continues to trouble me. LED is still off and I need to suspend the os (Fn+F1) and bring it back to life before it will recognise the existence of Bluetooth and enable wifi to work. Unfortunately, so far, with Smeegol, it does not recognise Bluetooth in spite of multiple attempts at suspending and resuming the system. I need to dig deeper and try to understand what is happening or supposed to happen upon resumption.

The other irritant on Smeegol so far - if I accidentally press the power button(and I seem to do that often while moving the netbook), a message is displayed that it will power-off after 30 seconds. However, it seems more like 3 seconds!

Figuring out how these buttons actually work along with the configuration files and code relating to them is one of the many pending items on my list of items I want to understand:(