-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22 Jan 2003 17:20:37 +0100, Mertens Bram wrote:
> Perhaps a dumb question, but would I have to reboot first and boot the > previous kernel before deleting the newer i386 and installing the > newer i686 kernel? > Or can I (while running kernel 2.4.18-19.7.x) > rpm -e kernel-2.4.18-19.7.x.i386 > rpm -i kernel-2.4.18-19.7.x.i686 > (same for kernel-debug)? Yeah, probably clever, because when you erase the files of your running kernel, it may be that it needs to load some kernel modules upon shutting down the system. But I doubt that. Hence I would reboot after installing the i686 kernel. Btw, the reason I did not suggest to -Uvh --force the kernel is that I want to avoid any trouble in case you no longer have any backup kernel installed at the time you read my mail. > > With glibc one way to upgrade from i386 to i686 is to downgrade > > (-Uvh --oldpackage glibc*.rpm) first to the previous glibc and then > > upgrade normally to the i686 version of the latest glibc erratum. > > Hmm I get dependency errors with this, isn't it possible to do a > --force? Install the i686 with --force over the current i386? Yes, possible. > [root@localhost rpms]# rpm -Uvh --oldpackage glibc-2.2.5-34.i386.rpm > error: failed dependencies: > glibc-common = 2.2.5-34 is needed by glibc-2.2.5-34 > glibc = 2.2.5-42 is needed by glibc-utils-2.2.5-42 > glibc = 2.2.5-42 is needed by glibc-debug-static-2.2.5-42 > glibc = 2.2.5-42 is needed by glibc-debug-2.2.5-42 That's why I suggested "glibc*.rpm". All-at-once solves dependencies. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+LtPX0iMVcrivHFQRArprAJ4gq86wuSV/XR3iw69Bd0EtNGuoyACdFYhA AHfFbyHSHWfH57dGbSrnxzo= =ojS9 -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
