<pre>> One possible way round this is to run your upgrade within a "screen"<br>> session. The upgrade will continue even if you get disconnected from<br>> the session, in which case you can reconnect later.<br>
</pre>That's what I did just now. Although I was a bit scared when I saw this:<br><br>Configuring dropbear<br> System startup links for /etc/init.d/dropbear already exist.<br>Restarting Dropbear SSH server: Connection to <a href="http://192.168.0.202">192.168.0.202</a> closed by remote host.<br>
Connection to <a href="http://192.168.0.202">192.168.0.202</a> closed.<br>imo@ivar-laptop:~$ ssh <a href="mailto:root@192.168.0.202">root@192.168.0.202</a><br><a href="mailto:root@192.168.0.202">root@192.168.0.202</a>'s password:<br>
root@om-gta02:~# screen -ls<br>No Sockets found in /tmp/screens/S-root.<br><br>... I don't know why, but somehow I did actually try 'screen -R' anyway, even though I saw the list was empty. And it did actually work. :)<br>
<br>I wouldn't call this a solution though, just a work-around.<br><br><br>-Ivar Mossin<br>