On 7/2/06, Paul Johnson <pauljohn32@xxxxxxxxx> wrote:
My Dell laptop hates the new kernel-2.6.17, so I remove it with yum remove kernel-2.6....
Okay.
Then I go about my business and find that the yum cron job has run and re-downloaded and re-installed that kernel. Goddam.
What else would you expect ?
Then I can put exclude=kernel-2.6.17* in /etc/yum.conf, but the problem just starts there. When yum runs, it finds updates for kernel modules on atrpms (for ipw3945 wireless) and livna (video card), and yum then fails because it cannot install those modules because it cannot install the new kernel. So I have to go back into /etc/yum.conf and exclude some specific versions of those modules.
That's exactly what it should do. You should just exclude al kernel related packages, or let yum be and use grub to boot to the kernel that works for you,
What a hassle. Seems to me that if a person manually removes something in yum, the system should respect that.
That would require special rules, and I would not consider such rules to be intuitive.
pj -- Paul E. Johnson Professor, Political Science 1541 Lilac Lane, Room 504 University of Kansas -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-- To be updated... -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
