Welcome to my world

Friend and colleagues laughing at you? Feel inferior? Need a really big machine?? Of course you do!
http://thrillingwonder.blogspot.com/2006/11/biggest-and-hungriest-machines.html

Max Spevack (Fedora Project Leader) yesterday announced some interesting stats about FC6. According to Max, since its release about 3 weeks ago, 300,000 unique IP addresses have checked for any updates to FC6. Wow! That’s at least 12,500 new installs per day!! Kinda pisses on DistroWatch’s stats! Oh and on a personal note… Take that Ubuntu boys!

Detailed stats are at: http://fedoraproject.org/wiki/ZodStats and you can read the whole release on fedora-announce-list.

Take a look at this!

[root@dyn89 yum]# pwd
/var/cache/yum
[root@dyn89 yum]# du -sh *
1.8M atrpms
6.1M core
5.3M development
11M extras
36K flash
84K jpackage-fedora
2.2M jpackage-generic
192K jpackage-generic-nonfree
848K livna
2.8M updates
176K updates-sourceThat’s 30Mb of crappy yum cache

Now take a look at this:

[root@dyn89 cache]# yum clean all
Loading "installonlyn" plugin
Cleaning up Everything
[root@dyn89 cache]# du -sh * 1.8M atrpms
12K core
5.3M development
12K extras
12K flash
84K jpackage-fedora
2.2M jpackage-generic
192K jpackage-generic-nonfree
12K livna
12K updates
176K updates-source9.6M much healthier

It nice to see something are just buried and not forgotten, Like corrupt RPM databases. A few years ago this was a common problem (common to me anyway!). The problem occurs either when two rpm process try and write to the rpm database in /var/lib/rpm or an impatient operator (like me) hits ctrl-c too many times.

When this happens, you rpm process (e.g. the rpm command or yum) would just hang. So why am I talking about this if the problem was fixed ages ago? Well it seem with the new funky yum-updatesd that’s included with FC6 is causing some problems.
You can see if your effected but running this command:

rpm -qa

If you get no output then you’ve screwed your databases. Here’s how to fix it.

1. Firstly su or sudo in to root
   su -
2. Clear your rpm caches
   rm -v /var/lib/rpm/__*
3. Now run the rebuild command
   rpm -vv --rebuilddb

You now gets some lovely healthy output showing you everything ok. It should look something like this:

D: adding 11 entries to Filemd5s index.
D: read h# 770 Header V3 DSA signature: OK, key ID 4f2a6fd2
D: +++ h# 1084 Header V3 DSA signature: OK, key ID 4f2a6fd2
D: adding "gimp-print-utils" to Name index.
D: adding 2 entries to Basenames index.
D: adding "Applications/Publishing" to Group index.
D: adding 12 entries to Requirename index.
D: adding "gimp-print-utils" to Providename index.
D: adding 2 entries to Dirnames index.
D: adding 12 entries to Requireversion index.
D: adding "4.2.7-22" to Provideversion index.
D: adding 1 entries to Installtid index.
D: adding 1 entries to Sigmd5 index.
D: adding "0beb1e4759ef5a92206941d9f0c9a52e0d546a2c" to Sha1header index.

You should now be able to install or upgrade using yum.

I’ve used VMware on Fedora since it because free. It’s great, No more rebooting to switch between Windows and Linux to use one application that just won’t work with WINE. Since upgrading to FC6, I have a problem running vmware-config.pl. Each time I ran it, I’d get error about config.h not being found. The simple (dirty) way to fix this is to do this:

touch /usr/src/kernels/`uname -r`-`uname -m`/include/linux/config.h

You should now be able to re-run vmware-config.pl without a problem.

Remember that you’ll need to do this each time you update the kernel.

Update I had a nightmare of a time getting this to work on a dual core Intel. It seems the Duos use i586 rather than i686. To fix you need to install the correct kernel devel version wget ftp://ftp.mirror.ac.uk/sites/fedora.redhat.com/updates/6/i386/kernel-devel-`uname -r`.i586.rpm
rpm -Uvh kernel-devel*.rpm then link to the correct linux.htouch /usr/src/kernels/`uname -r`-i586/include/linux/config.h

Update 2 I think I’ve found the cause of the above weirdness. Read More