-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28 Jul 2003 09:41:46 -0400, David Hart wrote:
> I finally got around to updating this weekend. First I installed the > 19.9 RPM and made sure that it was OK. > > Then I recompiled the source for NTFS read support and made a few other > changes - eliminating some of the bloat. Added ".NTFS" to the version > number. > > Reboot. Great. Works fine. > > While not essential, I went to delete 2.4.20-19.9 with an RPM -e and got > a list of dependencies. For example: > > "kernel >= 2.2.0 is needed by (installed) libpcap-0.7.2-1" > > Figuring that RPM was confused I rebuilt the DB. Same result. This was > the exact same procedure that I used with 2.4.20-18.9 without a problem. > > Now what? What is "strange" about system components requiring a "kernel" package to be installed? $ rpm -q --whatrequires kernel tcpdump-3.7.2-1.9.1 quota-3.06-9 prelink-0.2.0-18 pciutils-2.1.10-7 libpcap-0.7.2-1 rp-pppoe-3.5-2 vconfig-1.6-2 shapecfg-2.2.12-13 nfs-utils-1.0.1-3.9 iptables-1.2.7a-2 [...] If your customized kernel in non-rpm form is compatible with Red Hat's kernel, this would be an opportunity to make good use of rpm's --nodeps option upon erasing the last kernel package that is left. But why don't you keep the stock kernel as a backup kernel? - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/JT3z0iMVcrivHFQRAtciAJ9NAOntlReHjJZyuje6GofjRNSPrACbBGBe vAiUIUyzt8GCD6fGftf7B9k= =TP7+ -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
