Problem with Mandrake Update?

[killerasp]

Im using Mandrake 7.2. I used the Mandrake update utility to update the existing programs. But on some programs that install will take hours at a time. Is it recompiling the kernel? An example would be updating the MC (Mandrake Component program). It took me about 4 hrs to do, then restarted and said it was killing some programs (httpd, ETC). After that my Mandrake update utility and my Mandrake RPM wasnt working. WHAT THE HELL IS GOING ON???

[Molecule Man]

My advice, don't use mandrake update. If you use stuff from cooker it won't work, as that stuff is compiled for a Newer version of Glibc and RPM. Manually download the necessary security updates and wait for thenext version to come out of Beta.

[killerasp]

Do you mean from the Mandrake site where they list the updates for each version?

[sandy0]

Originally posted by killerasp:
[B]Im using Mandrake 7.2. I used the Mandrake update utility to update the existing programs. But on some programs that install will take hours at a time...... then restarted and said it was killing some programs. After that my Mandrake update utility and my Mandrake RPM wasnt working.... B]

I had the same problem...........really sucks! The problem is, I'm too new at this to even know what I need to update :) And my slow connection (56K) is not the best for huge downloads. I would have thought the update they mail you would contain "stable" stuff. It does give you the option of "normal" vs. "developmental" update and warns you that the "development" stuff could screw up your machine :) But I only did the "normal update" and still had the same problem you did. Sucks!

[frustratedlinuxnewbie]

Check your /var. MandrakeUpdate downloads the rpms in /var/cache/grpmi or somewhere like that. Eventually this will get full and all hell will break loose if you try to rpm. I know this sucks but you will need to clean this up. And if your logs do rotations maybe you'll need to clean some of them too. I hope this helps.

[sandy0]

Originally posted by frustratedlinuxnewbie:
Check your /var. MandrakeUpdate downloads the rpms in /var/cache/grpmi or somewhere like that. Eventually this will get full and all hell will break loose if you try to rpm. And if your logs do rotations maybe you'll need to clean some of them too.

It sounds like what you're saying is that the updater extracts the rpm files to some type of temp directory or "cache file" from the cd before installing them, much like the windows installer does with it's installer files or is done with zip files?? I know how to manually delete .tmp files in windows. Cache clearing is pretty automated in Windows. What's the best way to do this in Linux? (I suppose this is covered in some book :) I am not familiar with "rotating logs" or how to clean them, however :) Or with the term "rebind".

[frustratedlinuxnewbie]

d00d, not exactly what i meant but close :) . mandrakeupdate copies the rpm files to /var/cache during the fetch, then afterwards do the rpm. I don't know why the darn program can't respond properly when it can't fit the rpm files to the cache. I really think it should have some sort of exception handling. And I don't know if there's any automated way to delete them. What I do is as root move those files (as backup just in case I'll need them) in a separate partition. Oh, and this would mean you'll either do the rpm manually, or keep track of the size of the rpm files you're selecting in the mandrakeupdate. You can check how much space you have left using df. Oh, and for the rotating logs, check your /var/log if you have any .gz files. They're probably the backups of your log files. You can either delete them as root or move them to a separate partition. I hope this helps. :) If not, don't kill me :D

[ 05 March 2001: Message edited by: frustratedlinuxnewbie ]