[Bug 1319] Review request:BLCR - Berkeley Lab Checkpoint/Restart for Linux

RPM Fusion Bugzilla noreply at rpmfusion.org
Wed Jul 7 15:37:18 CEST 2010


http://bugzilla.rpmfusion.org/show_bug.cgi?id=1319





--- Comment #10 from Nguyen Son <nguyenkims at gmail.com>  2010-07-07 15:37:18 ---
(In reply to comment #9)
> > choose the right kmod for a package? For example, I have kernel 2.6.31 and
> > 2.6.32 installed, I install foo (which requires kmod-foo-kernel_version) in my
> > 2.6.31 , yum normally will automatically take kmod-foo-2.6.32 which certainly
> > will not work unless I reboot to use the new kernel?
> Have you taken a look at akmod packages; eg nvidia one, if it sees during boot
> that your kernel changed, it rebuilds the kmod, and loads that new module. This
> avoids delays between release of new kernels until rpmfusion builds normal
> kmods for that kernel (usually very quick, however). Its somewhat similar to
> how dkms used to work.
> 

No, what I means is that yum, instead of taking the *newest* kmod, should take
the one which correspond to the *actual* running kernel ( people normally has
some kernels installed but doesn't always use the newest one ). 

This situation can be avoied if yum use `uname -r` to decide which kmod version
correspdant.


-- 
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the rpmfusion-developers mailing list