Jim Conner wrote: > Ok, I just compiled it and copied the file over last night. I'll be testing > it soon. Would have been nice to know about how to just compile kdesud, my > poor P200mmx computer got pretty beat up yesterday compiling kdebase. :)
We had it running for about 30 minutes when my son suggested trying to just compile kdesud. We cd'd to the kdesud directory, ran make, 15 seconds later we had the kdesud file... Tested the theory by killing the kdebase compile (he has a K62-500, I'm not sure how close it was to finishing after that 30 minutes), running 'make clean' for kdebase to get rid of anything that may have been around to help the kdesud compile, running 'make clean' in the kdesud direcotry, then running 'make' in the kdesud directory and it worked beautifully. > When I updated from KDE 2.1 to KDE 2.2.1, I just ran the rpms in runlevel 3. > Would going to runlevel 3 and removing the DCOP and MCOP files in /tmp hurt > anything? AFAICT, no. I've done it several times with no issues. > ...I also left my ~/.kde2/share/* alone. I've emptied the cache with > the button in Konqueror's config panel, but maybe it's not deleting all the > files. I'll try cleaning some stuff up and see if that helps. If that doesn't work, bite the bullet and start with a fresh .kde2 directory. Just 'mv .kde2 .kde2old' (choose whatever directory name you want) from runlevel 3 and then switch back to runlevel 5. The .kde2 directory will be automagically created for you. I had to resort to this not too long ago because KDE wouldn't remember my clock settings (wanted 12-hour time, not 24-hour time). KDE's been much more stable for me since then. > > Jim > > Good luck, Tim <snip> _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
