On Tue, Mar 21, Richard Biener wrote:
On Tue, 21 Mar 2017, Thorsten Kukuk wrote:
On Tue, Mar 21, Richard Biener wrote:
So what issue are we solving then? That is, is this for CaaSP only where we can guarantee the r/o root?
The problems we want to solve are all the broken systems you can regular read on the factory list about after an update, because the update in the running system did break other running processes. Especially the Desktop.
Sure. But do we now exchange this for all the broken systems where replacing root with the snapshot after the transaction? And are we sure the number of broken systems will actually shrink with this change? (and can you prove that?)
Sorry, but I neither understand what you are writing here nor what your problem is. What I can prove is: all the problems the people had with updates, that their running applications did crash and the update did not finish and their system were left over in a unbootable state can be solved with this. And about your fear about that the snapshot is in a broken state after update even if zypper did not return any error: if this happens, this would also happen with your normal running system. It does not matter if you update a snapshot or the real system, the installed RPMs are the same. And, don't forget: if you don't like transactional updates, nobody is forcing you to use them. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org