> One possible way round this is to run your upgrade within a "screen" > session. The upgrade will continue even if you get disconnected from > the session, in which case you can reconnect later.
That's what I did just now. Although I was a bit scared when I saw this: Configuring dropbear System startup links for /etc/init.d/dropbear already exist. Restarting Dropbear SSH server: Connection to 192.168.0.202 closed by remote host. Connection to 192.168.0.202 closed. [EMAIL PROTECTED]:~$ ssh [EMAIL PROTECTED] [EMAIL PROTECTED]'s password: [EMAIL PROTECTED]:~# screen -ls No Sockets found in /tmp/screens/S-root. ... 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. :) I wouldn't call this a solution though, just a work-around. -Ivar Mossin
_______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
