Hi, On Tue, 21 Mar 2017, Thorsten Kukuk wrote:
On Tue, Mar 21, Michael Matz wrote:
Um. I'm not sure how to say this, but you do know that NTFS provides snapshots as well and Windows makes use of them for update purposes much similar to our rollback scenario with btrfs?
If it is used for Windows Updates it does not work in practice, else the windows installation on my laptop wouldn't go in a corrupt state unrepairable by Windows by an update. And only wikipedia assumes that the Windows Update is using it, Microsoft itself is not mentioning it. Ah, wait, yes, Windows can do a rollback and Microsoft explains it, but at first you need to get the current broken state booting to start the GUI to do the rollback ... If there are other ways, MS is hiding them well in their documentation.
Like us they can boot from a snapshot (or rather at boot time you can restore a snapshot from the "emergency initrd" (which even has graphical user interface!)). Depending on Windows installation and settings snapshoting is not always active (like with us), and sometimes they remove snapshots too early. But sure: they have bugs, that's no wonder. Us too, if I may be so bold :) (that your laptop can't be recovered is not a good data point; my sometimes-windows-gaming desktop was recoverable (and actually needed it only once in the whole lifetime, unlike us when we botched the bootloader installation for the 20th time), so can I say now that it does work in practice? :) ). In any case bugs in their implementation of it don't directly show an inherent flaw in their approach. I do see some problems with that approach, but far fewer than in the transactional-updates approach. But I guess somebody will have to properly implement the initrd approach for us so that we can really compare both on the system we care about. After all, possibly I'm wrong ;) Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org