I have been running an openSuSE 11.4 system with a number of server applications such as Tomcat, James, Bacula etc., and decided it was time I upgrade it to 12.3. I have always followed a model of keeping /home in it's own partition and installing each new version of openSuSE into it's own partition. In this way, my thinking was that I could keep running the older version of openSuSE until I get all the servers and configuration files (found in /etc /srv and elsewhere) upgraded and running under the newer version of openSuSE. That model has always worked in the past and I thought openSuSE developers would continue to adhere to that model as well... In other words, I thought that things, such as configuration files for user applications, put in user's /home directories would stay backwards compatible with future versions of openSuSE and we could upgrade/migrate them at our leisure, if/when we wanted to.. Well, that model, has failed this time on me. After installing openSuSE 12.3, I restarted my 11.4 system and found that there were several akonadi processes that were collectively running the CPU at 100% capacity and within a few minutes the 11.4 system would completely lock up on me forcing me to hard reboot the system... This strongly indicated that the 12.3 installation of openSuSE touched/changed configuration files in the /home user directories, in such a way that broke 11.4, which comes as a surprise.... AND it is scary because I do not know what all got touched/changed. I know that I am making a large version jump in openSuSE, but I thought the whole idea/suggestion of putting /home in a separate directory was to allow exactly this sort of thing, to be able to run different versions of openSuSE with a "constant" home directory. If a change in a configuration file, found on the /home directories, is absolutely necessary, then why not use a scheme that uses some sort of versioning markers or perhaps links and environment variables to differentiate what config (or part of a config) file goes with what version of it's associated application or OS? It really seems like /home dirs and files should stay functional no matter what version of openSuSE is running, and these files should never break the OS. Seems like configuration files that are highly OS dependent should be under /etc Doing some internet searches, I found a set of instructions at http://forum.kde.org/viewtopic.php?f=154&t=88771&start=15 which described how to disable akonadi. This was done by renaming a bunch of files (as described in this forum) which are found in the users home directory under various .directories. By disabling akonadi, the 11.4 system is able to run ok, but I am not familiar with akonadi and the descriptions of it is not helping me to grok what the impact of disabling it may be on the 12.3 system. I don't know if I will need akonadi or not in the 12.3 version of openSuSE, and since it was enabled and running after the installation, I fear I might be in for some agonizing debugging if things do not work correctly in 12.3. So how should I best proceed? Is there a way to disable akonadi when I am running 11.4 and enable it when I am running 12.3 automagically? Marc.... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org