On 2016-12-29 14:30, Richard Brown wrote:
On 29 December 2016 at 12:53, Carlos E. R. <> wrote:
On 2016-12-29 13:49, Robert Kaiser wrote:
I have. Whole desktop crash during upgrades. I run zypper in a text mode console for that reason.
and that's why my 'zypper-twup' alias does "sudo screen zypper dup --no-allow-vendor-change"
Does screen survive when started from a graphical terminal? I thought you needed to have it running from console. That's what I do: ctrl-alt-f1 login as root start "screen new" ctrl-alt-f7 screen atach (I use tmux, rather) run zypper. Which is, effectively, running zypper in console.
The screen means the upgrade will continue regardless of whether or not the desktop or tty I am running it from explodes spectacularly, even though it happens very rarely.
Yes, it is rare, but I have seen it happen, specially as I don't upgrade TW every week.
for the equivalent of 'zypper up', openSUSE GNOME also takes care of this problem by using the GNOME Software update mechanism. Packagekit downloads all of it's patches, then offers the user to reboot to install them. When that user choses to reboot, systemd boots into a special 'upgrade' target, which only patches the system and then reboots again into the patched system.
Interesting. I don't use gnome recently, nor package kit, though.
This is a stupid way of doing things, of course doesn't do the upgrade as completely as a dup --n-a-v-c would, but it does avoid the problems of desktop crashes during upgrades borking upgrades using a graphical tool at least.
In the future, I'm most excited about the prospect of proper 'transactional updates' for Tumbleweed, such as you can see working in concept here: https://github.com/thkukuk/transactional-update
Requires btrfs (snapshots and volumes). I have seen a similar concept on expensive systems running unix. They basically changed links to the old/new files. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)