<br><br><div class="gmail_quote">On Sat, Jun 19, 2010 at 12:16 AM, Bruno Wolff III <span dir="ltr"><<a href="mailto:bruno@wolff.to">bruno@wolff.to</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Jun 18, 2010 at 22:02:49 -0400,<br>
<div class="im"> Marcel Rieux <<a href="mailto:m.z.rieux@gmail.com">m.z.rieux@gmail.com</a>> wrote:<br>
><br>
</div><div class="im">> As I said, I don't believe rpmfusion, a repository not supported by Red<br>
> Hat/Fedora, could block a kernel update.<br>
<br>
</div>They can using 'conflicts' in the spec file. </blockquote><div><br>What's this spec file? How do you use conflicts?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If the kmod is installed first,<br></blockquote><div><br>How do I make "if" less iffy?<br><br>You'll have to explain this whole process. I'd be very surprised if a repository not belonging to Red Hat/Fedora could prevent a kernel upgrade or any upgrade. This could eb dangerous.<br>
</div><div> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You can also set your system so that the default boot kernel doesn't change<br>
when there is a kernel update. This protects you from the kmod being released<br>
late problem at the cost of having to manually switch boot kernels after<br>
every kernel + kmod update.<br></blockquote><div><br>If you remember the beginning of this discussion, we were talking about the problems the missing kmod could occcasion to <B>newbies</B>. I always check that the corresponding kmod is there and if I'd ever forget, it would be no problem reverting to the previous kernel. But a newbie might decide that "this thing doesn't work" and go back to Windows.<br>
<br>Your "solution" is not a solution for newbies.<br><br>Now, here's the upgrade suggestion I received today:<br><br>Package kernel.x86_64 0:2.6.32.14-127.fc12 set to be installed<br>---> Package kernel-firmware.noarch 0:2.6.32.14-127.fc12 set to be updated<br>
---> Package kernel-headers.x86_64 0:2.6.32.14-127.fc12 set to be updated<br>---> Package kmod-nvidia.x86_64 1:195.36.24-1.fc12.3 set to be updated<br>--> Processing Dependency: kmod-nvidia-2.6.32.14-127.fc12.x86_64 >= 1:195.36.24-1.fc12.3 for package: 1:kmod-nvidia-195.36.24-1.fc12.3.x86_64<br>
<br>kernel x86_64 2.6.32.14-127.fc12 updates 21 M<br>kernel-firmware noarch 2.6.32.14-127.fc12 updates 973 k<br>kernel-headers x86_64 2.6.32.14-127.fc12 updates 754 k<br>kmod-nvidia x86_64 1:195.36.24-1.fc12.3 rpmfusion-nonfree-updates 31 k<br>
<br>It somehow doesn't seem to me like a standard upgrade...<br></div></div><br><br>