2007/7/21, Kevin J. Cummings <cummings@xxxxxxxxxxxxxxxxxx>:
antonio montagnani wrote: > 2007/7/21, Kevin J. Cummings <cummings@xxxxxxxxxxxxxxxxxx>: >> antonio montagnani wrote: >> > I updated kernel yumming it >> > >> > 1) at reboot, the madwifi driver from freshrpms didn't build against >> dkms >> > 2) after upgrading I should have the following two kerenels: >> > >> > 2.6.22.1-27 >> > 2.6.21-1.3228. >> >> Which kernel were you actively running when you upgraded. My >> understanding is that the yum installonlyn plugin keeps the new one and >> the one you are currently running. If you have a newer one you are not >> currently running, it punts it in favor of the new one. >> >> > surprise!!! I found 2.6.21-1.3194 but no 2.5.21-1.3228 > I was running the newest 2.6.21-1.3228 and not the oldest 2.6.21-1.3194 > > Very strange, isn't it??? Well, if your logs back you up, then bugzilla it as a bug in yum (more importantly in the yum installonlyn plugin), and be prepared to show your proof in the bug report. I can almost guarantee the first thing the maintainer is going to do is question which kernel you were running. B^) -- Kevin J. Cummings kjchome@xxxxxxx cummings@xxxxxxxxxxxxxxxxxx cummings@xxxxxxxxxxxxxxxxxxxxxxx Registered Linux User #1232 (http://counter.li.org) -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
tnx Kevin, 1) I went through yum.log and I cannot see what was set to be erased.In yum.log I read: Jul 21 00:29:16 Updated: cairo.i386 1.4.10-1.fc7 Jul 21 00:29:17 Updated: gnome-python2-extras.i386 2.14.3-4.fc7 Jul 21 00:29:25 Updated: autofs.i386 1:5.0.1-20 Jul 21 00:29:26 Updated: gnome-python2-gtkmozembed.i386 2.14.3-4.fc7 Jul 21 00:30:20 Updated: seamonkey.i386 1.1.3-1.fc7 Jul 21 00:30:26 Updated: gnome-python2-libegg.i386 2.14.3-4.fc7 Jul 21 00:32:41 Updated: thunderbird.i386 2.0.0.5-1.fc7 Jul 21 00:32:45 Updated: mdadm.i386 2.6.2-4.fc7 Jul 21 00:32:46 Updated: gnome-python2-gtkhtml2.i386 2.14.3-4.fc7 Jul 21 00:43:29 Installed: kernel-devel.i686 2.6.22.1-27.fc7 Jul 21 00:44:56 Installed: kernel.i686 2.6.22.1-27.fc7 Jul 21 00:45:18 Updated: kernel-headers.i386 2.6.22.1-27.fc7 and in rpmpkgs: kernel-2.6.21-1.3194.fc7.i686.rpm kernel-2.6.21-1.3228.fc7.i686.rpm kernel-devel-2.6.21-1.3194.fc7.i686.rpm kernel-devel-2.6.21-1.3228.fc7.i686.rpm kernel-headers-2.6.21-1.3228.fc7.i386.rpm in rpmpkg.1 kernel-2.6.21-1.3194.fc7.i686.rpm kernel-2.6.21-1.3228.fc7.i686.rpm kernel-devel-2.6.21-1.3194.fc7.i686.rpm kernel-devel-2.6.21-1.3228.fc7.i686.rpm kernel-headers-2.6.21-1.3228.fc7.i386.rpm Where do I read the full story (erased, updated, added)?? 2) what is really funny, I cannot read the following files aslo as root by clicking on them, but I can open by gedit!!! yum.conf [main] cachedir=/var/cache/yum keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 metadata_expire=1800 # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d yumex.conf [yumex] autorefresh = yes filelists = no recentdays = 14 autocleanup = yes proxy = exclude = debug = no mirrordetection = default nofastestmirror = 0 : /etc/yum/pluginconf.y/installony.conf [main] enabled=1 # this sets the number of package versions which are kept tokeep=2 3) The madwifi-0.9.3-2.fc7.i386.rpm from freshrpm doesn't build the module at start-up by dkms, so I don't have wireless card operating!!! Shall I file a bug (for madwifi not o.k.) against Fedora or Freshrpms?? -- Antonio Montagnani Skype : antoniomontag
