Stuart Prescott wrote: > > Possibly -- but would they use network manager in such a situation? (I don't > know). My feeling is that it would be fairly uncommon to upgrade over ssh for > machines that actually used network manager; the intersection of > upgrade-over-ssh and users of network manager (which is a desktop-centric > tool) would seem small.
Yeah, I do not recommend NM on servers (and the package description clearly states this) or in static environments like a workstation in a lab, where you might upgrade the system over ssh. > As such, I had thought it was probably just a "document that you shouldn't do > this" situation rather than an RC bug in network-manager. In the same way > that upgrading over telnet or within a gdm session is not supported, this is > just documented rather than being a grave bug in the package. See section > 4.1.4 of the etch release notes (which is currently unchanged in the lenny > release notes) which explicitly warns against upgrading within a telnet, > rlogin, rsh, xdm, gdm or kdm session. > > I doubt this is something that can or will be cured before lenny releases so > I'm guessing that this is going to be "fixed" by documentation for the time > being at least. (Which is why I flagged it as an issue in the release notes > wiki.) Well said. Honestly, there is no easy fix for this. Either we restart network-manager, or we tell the user to reboot the system. But for the latter, there is no infrastructure in Debian to do this in a structured way. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
