I wanted to upgrade my desktop machine at work to the latest version of Ubuntu, but since it takes several hours to upgrade an Ubuntu host, and I have work to do during the day, I figured I could log into my workstation from home in using ssh and start the upgrade remotely.
So I logged into my workstation from home and ran:
> sudo apt-get install update-manager-core > sudo do-release-upgrade
The upgrade script warned me that I was using ssh and asked if I was sure I wanted to continue. I said “Y”, and a little while later the upgrade manager was busy downloading upgrade packages.
I planned to check it a couple of times that night, answer any package upgrade questions that popped up, and then in the morning when I got to work the upgrade would be complete.
Of course what actually happened was that I got side-tracked onto some other problem that night, forgot about the upgrade in progress, and when I got to work the next day my workstation was in a state of limbo, with the upgrade halfway complete, waiting for me to answer some question on the screen — at my house.
Luckily the Ubuntu developers who created the ssh upgrade process run that upgrade inside of a screen session. As the screen pages states, “Screen is a full-screen window manager that multiplexes a physical terminal between several processes (typically interactive shells).”
So at work all I had to do was get the list of current screen sessions:
> sudo screen -list There are screens on: 9129.ubuntu-release-upgrade-screen-window (05/17/2011 08:50:08 PM) (Attached) 2 Sockets in /var/run/screen/S-root.
Invoke screen using the “-d -r sessionowner/[pid.tty.host]” flags:
> sudo screen -d -r root/9129.ubuntu-release-upgrade-screen-window
… and I could pull up the screen at work that had been displaying at my home. Once I answered the remaining questions about whether to keep my custom configuration files or use the new, packaged configuration files my workstation rebooted and the latest version of Ubuntu booted right up.