Hi, first a word on Mozilla. Most of us know that the newest stable version can be found on ftp://ftp.suse.com/pub/projects/mozilla This directory does not appear to be on any of the mirrors. I have just found the beast on the mirrors - go to (for example) i386/supplementary/GNOME/update_for_8.0/base/ Which is (I am sure) the only logical place to hide it ;-) Now to kde. I spend quite a bit of time in mozilla under kde. While the Konq hardly ever aborts on me, Mozilla is a lot less stable. This is my second attempt at writing this mail because the first one got lost when Mozilla died when my DSL connection timed out. The original 8.0 versions of kde3 and Mozilla were just plain instable, the newest versions are a bit better. When I start Mozilla, moving the mouse before it has completely loaded often causes it to fail to load. This failure in turn often then causes kdeinit to terminate (error message: something to do with DCOP) which means I have to exit kde, kill the startx session with .ctrl.C and try again. I wonder if other people recognise those symptoms. A while ago, I cleaned up my /tmp directory. This left me totally unable to start X11 (kde) at all. Not even knowing what the problem was, I finally ended up re-installing virtually the entire system except for /home. That will teach me to take backups - mea culpa. This brings me to the 8.0 release itself. I am used to 'tailoring' releases (especially on the servers I control) to batten them down against crackers. This is something that I do not feel able to do with 8.0. Cause and effect are sufficiently opaque to me (wiping /tmp and thus killing kde is the worst example) that there is no way I could upgrade any of 'my' servers to this level. They will remain on 7.3 for the time being, the most likely upgrade path at the moment being Slackware. KDE is not even an issue there, they do not have X at all. I have DSL here. Without DSL to download the updates, this version of SuSE would have been a total mess. My first SuSE level (5.1 or something) was essentially *stable*, as were most of the others I have used since. Going very off-list (kde) here, yast2 cannot handle initial upgrade installation when read-only partitions are present, even if these are mounted as something like /cd_doc_copy. None of yast2's business! Upgrading my laptop was a total mess, with frequent stops where I had to reboot and restart. The error-message (if one came at all) was 'spurious 8259a interrupt: IRQ7'. This turned out to mean that SuSE 8.0 did not like my Logitech wheel-mouse, something that 7.3, 7.2, 7.0 and so on down had been quite happy with (ok, I used yast1 for all of them). This turned into a rant so a </rant> is appropriate here. Hopefully 8.1 will be an improvement. -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html