[maemo-users] WiFi borked after update

From: hendrik at topoi.pooq.com hendrik at topoi.pooq.com
Date: Thu Oct 9 06:13:13 EEST 2008
On Wed, Oct 08, 2008 at 01:48:24PM +0300, Marius Vollmer wrote:
> "ext Denis Dimick" <dgdimick at gmail.com> writes:
> > I agree that updating over a network should, and does work from a
> > "normal" Linux distro, however, I'm not sure it's going to work on
> > Maemo anytime soon; I'm guessing the small memory footprint prevents
> > some of the applications from not killing off a SSH session when
> > there's an upgrade.
> Ahh, no, the browser daemon might get swapped out, but there is more
> than enough memory to keep a ssh session going during an upgrade.
> Upgrades don't take that much ram anyway, the danger is to run out of
> 'disk' space.
> My guess is that it is just the way our non-standard network
> configuration mojo works: if the icd2 daemon gets updated, it takes the
> network down with it during replacement.  I am not sure about this,
> maybe it is just a small bug somewhere, or maybe it is a big design flaw
> of our network configuration mojo, or something inbetween.  We just need
> somebody to care and fix it.

Debian warns not to do an upgrade over X, because X will go down and 
up when it is reinstalled, and then your upgrade will hang.  I suspect 
this is less of a problem when the X server is running on a different 
machine from the one being upgraded.

I don't recall any such warning for ssh, though.  ssh connections seem 
to stay up even when the ssh demon is replaced, perhaps because the ssh 
demon is only involved in starting connexions, not in maintaining them.

-- hendrik

More information about the maemo-users mailing list