after some more investigation, ive found its the glibc-devel rpm which is broken, somehow the installed version doesn't like being touched in any way. for now i've done a rpm -e --justdb glibc-devel, so at least you wont see it and want to update it. any kind of manipulation of the glibc-devel rpm, either uninstall, reinstall, upgrade, etc, causes rpm to grow and grow until it reaches 1.8gb and runs out of swap space. Anyone any ideas? Ewan On Sat, 2002-07-27 at 14:48, Fred A. Miller wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday 26 July 2002 8:12 pm, Ewan Leith wrote:
Im having the same problem, specifically with the glibc updates.
If i run it in text mode it seems to work ok, but the graphical mode causes a kernel panic saying it cant handle a paging request from rpm.
If i get time over the weekend i will try and figure it out, but for now running yast2 in text mode to get past the problem upgrades seems to be the fix.
I had the same problem on my box at home, but somewhere along the "line" of updates, it got fixed. I'd reccomend that you use the text mode and update EVERYTHING that Yast selects, INCLUDING KDE 3.02!! Yes....DO choose it for update, even though it will mark as "G" when you select it. Select again till you see an "X." Reboot and see if Yast will work in KDE.
Fred
- -- Fred A. Miller Systems Administrator Cornell Univ. Press Services fm@cupserv.org, www.cupserv.org - --- SuSE Linux v8.0 Pro, KMail 3.0.1--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj1CpMMACgkQB9vk4ichYXfTRwCeNvkYrDPsU7njbmwBJpFBhN6k 10QAnA5UOO7VkYCl0uaRNHGMyiIt0nGN =S+Qw -----END PGP SIGNATURE-----