Re: keeping kmod-nvidia and kernel upgrades "in sync"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/11/06, Dr. Michael J. Chudobiak <mjc@xxxxxxxxxxxxxxx> wrote:
>> > My guess is that livna hasn't caught up with the kernel yet.
>>
>> No, it hasn't. So why does yum pull in a new kernel, if kmod-nvidia
>> depends on the old kernel?
>
> Because you're not upgrading kmod-nvidia.  The kernel has absolutely
> no dependencies on kmod-nvidia, its the other way around.

Well, yum has all the package dependency info in its metadata, so why
can't it apply it both ways (i.e., kernel -> kmod, and kmod -> kernel)?

But more urgently: what's the best way to ensure that you don't have a
non-functioning computer in the morning, because of a driver/kernel
mismatch? Do I have to exclude kernel and kmod* from yum updates?

I don't understand how the lack of the nvidia driver renders a
computer non-functioning.  However, not relying on 3rd party yum
repositories for kernel modules seems like the best course of action.


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama@xxxxxxxxx
LlamaLand                       http://netllama.linux-sxs.org


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux