You know, I wish someone would document the model that they are using for the installation of tomcat6 under SuSE. I am running SuSE11.0 and just got a security update for it. The rpm failed to install because it was expecting a different organization of the directories for Tomcat6 and could not change the name of the Catalina directory under /etc/tomcat6/Catalina. The new rpm was trying to change this to a link to point to /var/cache/tomcat6/Catalina Almost every version of SuSE has come out with a different directory organization for Tomcat and it NEVER follows the simple single root hierarchy of directories that the Jakarta Apache folks suggest and release Tomcat in. This constant reorganizing of Tomcat, (and it sometimes happens even within a single SuSE release, as happened this time) is proving to be a maintenance headache and I constantly am having to debug, fix and repair links and directories to follow suit. While I understand the addition of some of the scripts for controlling tomcat as a service, why can't the organization of the tomcat directories follow the same simple hierarchical directory pattern that developers over at Jakarta Apache release it in? Why is it necessary to break it up and have all these links, all over the place, piecing it back together? It might suit some few people to organize it differently, but for most of us KISS and Standards are the principals to best use. And without a description of the model that someone is trying to use, it makes it nearly impossible to understand the rational for organizing it the way it is being done under SuSE. Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org