On Du, 03 iul 11, 14:04:21, Curt wrote:
>
> What's wrong with just doing "apt-get -d dist-upgrade" first, thus
> rendering the whole question of NM dropping the connection or not moot.
>
> Or am I missing something?
Yes, network-manager is not restarted during package download, but
during packa
On Sat, 02 Jul 2011 21:29:12 -0400, Nico Kadel-Garcia wrote:
> On Sat, Jul 2, 2011 at 5:10 AM, Camaleón wrote:
>> On Sat, 02 Jul 2011 01:47:38 +, Hendrik Boom wrote:
>>
>> (...)
>>
>>> Or is there some devious trick I'm missing? Will an ssh connection
>>> from another machine survive the upg
On Sun, 03 Jul 2011 14:04:21 +, Curt wrote:
> On 2011-07-02, Camaleón wrote:
>>
>> And of course, warning about NM can leave the system disconnected is a
>> very good point (I didn't know NM can take that path...), so in the
>> evnt this can happen and the OP is using NM, he can just turn it
On 2011-07-02, Camaleón wrote:
>
> And of course, warning about NM can leave the system disconnected is a
> very good point (I didn't know NM can take that path...), so in the evnt
> this can happen and the OP is using NM, he can just turn it off before
> doing the upgrade and turn it on aftwew
On Sat, Jul 2, 2011 at 5:10 AM, Camaleón wrote:
> On Sat, 02 Jul 2011 01:47:38 +, Hendrik Boom wrote:
>
> (...)
>
>> Or is there some devious trick I'm missing? Will an ssh connection from
>> another machine survive the upgrade process, for example?
>
> Yes, I would try that way.
>
> Given yo
On Sat, 02 Jul 2011 14:34:46 -0400, Joey Hess wrote:
>
> (However, sshing in to upgrade a system running network manager does
> indeed not work; while I feel it's a serious bug the bug report about
> that has still not been dealt with sadly.)
>
Maybe I missed it, but it doesn't even appear to b
Hendrik Boom wrote:
> But I'm stuck. The next step is to issue
>
> apt-get dist-upgrade
>
> but I can't figure out where to type this in. I can log in using gdm,
> but terminals found there may expire during the upgrade, leaving
> everything in an inconsistent state.
Debian takes care to kee
On Sat, 02 Jul 2011 14:16:54 +, Camaleón wrote:
> On Sat, 02 Jul 2011 13:54:02 +, Curt wrote:
>
>> On 2011-07-02, Camaleón wrote:
Let’s just say that GDM is a good indicator of someone also using NM.
>>>
>>> A notebook or a portable system is more inclided to be an indicator
>
On Sat, 02 Jul 2011 13:54:02 +, Curt wrote:
> On 2011-07-02, Camaleón wrote:
>>>
>>> Let’s just say that GDM is a good indicator of someone also using NM.
>>
>> A notebook or a portable system is more inclided to be an indicator for
>> NM presence but not a DE or a display manager :-)
>>
>>
On 2011-07-02, Camaleón wrote:
>>
>> Let’s just say that GDM is a good indicator of someone also using NM.
>
> A notebook or a portable system is more inclided to be an indicator for
> NM presence but not a DE or a display manager :-)
>
> I disable NM in all of my workstations that run GNOME.
B
On Sat, 02 Jul 2011 14:01:18 +0200, Claudius Hubig wrote:
> Camaleón wrote:
>>I run GDM and NM is off :-)
>
> Let’s just say that GDM is a good indicator of someone also using NM.
A notebook or a portable system is more inclided to be an indicator for
NM presence but not a DE or a display mana
Camaleón wrote:
>I run GDM and NM is off :-)
Let’s just say that GDM is a good indicator of someone also using NM.
>But I take your point: if NM is not even capable of surviving from a
>remote ssh session then here you have a very good reason to disable it
>ASAP.
It ‘simply’ drops all network
On Sat, 02 Jul 2011 13:13:22 +0200, Claudius Hubig wrote:
> Camaleón wrote:
>>On Sat, 02 Jul 2011 01:47:38 +, Hendrik Boom wrote:
>>
>>(...)
>>
>>> Or is there some devious trick I'm missing? Will an ssh connection
>>> from another machine survive the upgrade process, for example?
>>
>>Yes,
Claudius Hubig writes:
> If you absolutely have to use an SSH connection, install screen
> beforehand and run the upgrade from inside screen, so it can continue
> when the connection drops.
You can also use screen in a terminal in an X session. It will survive
quitting X, and you can reattach t
Camaleón wrote:
>On Sat, 02 Jul 2011 01:47:38 +, Hendrik Boom wrote:
>
>(...)
>
>> Or is there some devious trick I'm missing? Will an ssh connection from
>> another machine survive the upgrade process, for example?
>
>Yes, I would try that way.
>
>Given your current situation I'd say a SSH
On Sat, 02 Jul 2011 03:14:12 -0400, William Hopkins wrote:
> On 07/02/11 at 01:47am, Hendrik Boom wrote:
>>
>> I'm in the middle of the upgrade from lenny to squeeze. I have a
>> partially working system. I've been following the instruction ins the
>> release notes,
>> http://www.debian.org/rel
On Sat, 02 Jul 2011 01:47:38 +, Hendrik Boom wrote:
(...)
> Or is there some devious trick I'm missing? Will an ssh connection from
> another machine survive the upgrade process, for example?
Yes, I would try that way.
Given your current situation I'd say a SSH session would be more than
On Fri, 01 Jul 2011 23:54:39 -0500, Brian Ryans wrote:
> Quoting Hendrik Boom on 2011-07-01 20:47:
>> And I can't use cntl-alt-F1 to get a text console, because all I get is
>> a blank black screen. Is gdm taking over the text consoles and
>> disallowing them? How do I get my text consoles back
On 07/02/11 at 01:47am, Hendrik Boom wrote:
>
> I'm in the middle of the upgrade from lenny to squeeze. I have a
> partially working system. I've been following the instruction ins the
> release notes, http://www.debian.org/releases/stable/amd64/release-notes/
> ch-upgrading.en.html and I've g
Quoting Hendrik Boom on 2011-07-01 20:47:
> And I can't use cntl-alt-F1 to get a text console, because all I get is a
> blank black screen. Is gdm taking over the text consoles and disallowing
> them? How do I get my text consoles back so I can proceed with the rest
> of the upgrade?
Try ctr
20 matches
Mail list logo
