Eberhard Moenkeberg wrote:
On Thu, 16 Feb 2006, Thomas Hertweck wrote:
[...] Sorry, no hand-crafting involved here. I could do the "update" without problems (YaST does not stop me) and doing so, I could "destroy" my current installation. We both know what the correct way is to perform an entire system update, but YaST does in this case not stop me from doing the wrong thing... Thus, the only statement I can make: I can't reproduce what you've said. If YaST did indeed stop users from doing an entire system upgrade with the "System Update" module, then the SDB article cited earlier would not make any sense (as according to you that problem should never happen). Hmm...!??
From where to where? Not from 9.0 to 9.1, and I guess not from 9.3 to 10.0.
It has already been mentioned in my last email: 9.2 -> 9.3 (that system is available to me and that is the system where I made a test). Well, I think there has never been such a functionality in YaST "system update" to protect users from trying a system upgrade to a completely new SUSE version, and that is the reason why we have seen not only one problem report related to this issue on suse-linux (de) over the years (in fact, there were dozens), and that is also a reason why there is an SDB article about this issue - all of that would not have happened if you were fully right. Something is a bit mysterious here... Cheers, Th.