gedan.net

Please make sure to backup important files before starting the upgrade process. The upgrade should work without problems, but for your own safety: Backup your datas!

Update 2009-05-24: Please read the comment from Paul W. Frields (Thank you, Paul!) regarding the upgrade process before following this tutorial. I recommend you to wait until Leonidas is officially released and to not use the Rawhide-branch. (The procedure will be the same as mentioned here, but without the “Display unstable test releases above” check box setting.)

As you may have seen from the banner I’ve installed on the upper right at my webpage, Fedora 11 Leonidas will be here in the next few days.

All of you using Fedora 10 right now and who can’t stand the wait to upgrade to Leonidas there is a way to upgrade today to the last snapshot of the yet unreleased version of Fedora 11 Leonidas.
Continue Reading

I had a strange error within my last yum update command. I got these error

rpmdb: Thread/process xxxxx/yyyyyyyyyy failed:
Thread died in Berkeley DB library

and yum stuck in the mid of the update process. This might have been due to an compromised ext-filesystem, as my laptop didn’t shutdown properly and maybe the journal got cluttered.

However, there is an easy way to get thinks back to a working state (at least for me), which might help others:

rm -f /var/lib/rpm/__db*
rpm –rebuilddb

yum clean all
yum check-update

The first two lines remove the old database entries and rebuild the Berkely database. Make sure, that there are no other yum-services running while rebuilding the database (at least this is, what has been said in the bug-reports). The second two lines clean the yum cache and update the package lists. Yum should run without database errors now.

The error has multiple hits (though it’s obviously not a bug) on the Fedora bug-tracker (bug#471411, bug#468437, bug#462314, bug#479818 and bug#45303)

I recently installed the Wordpres StatPress-Plugin. This plugin can give you real-time information about your blog visitors. It also detects web-spiders and search-engine bots automagically, so you can seperate them from regular visitors.
However, the reason for this post was not to promote this plugin, rather than giving you some insight about what StatPress has to say about my blog visitors.

Summarized to an unordert list this leads to

• 72 visits (52 pageviews) on a single day, with as yet actually not any interesting posts
• 57,9% from Germany, 36,8% from US
• 12 unique visitors, so most visits seem to be bots and spiders
• 15 detected spider visits (53% Google Feedfetcher)
• 15 RSS2 suscription (most probably the spiders?)
• 93,1% Linux systems (hurray!)

Continue Reading