Re: Debian safe-upgrade to 6.0.2 - don't run within X session

On Tue, Jun 28, 2011 at 12:25 AM, Scott Ferguson <
prettyfly.productions@xxxxxxxxx> wrote:


Opening a vt will do nothing to "protect" any running x-apps. If
concerned about x-apps whilst doing an upgrade - logout of x and login
to a console then shutdown x.


I'm afraid users could be confused by this and other statements.
There is a point to the original post which seems to be missed.

Logging out of X can be done, but optional as long as you
don't have important work to save within X applications.
What is "login to a console" in your description?
It is basically a VT or ssh in remotely. A VT is very
valuable and we should avoid referencing it negatively
so everyone understands regardless of their usual language.

I don't think some people "get it" in terms of why I posted this.
Please read and consider fully...

Doing a dist-upgrade is a major upgrade. It is done not so often and
done with the Debian upgrade guide nearby. It tells
us very clearly to do dist-upgrade within a VT console or over ssh
session, and not within X. End of debate on that.

Doing safe-upgrade (I refer to aptitude command line args here)
is done very often, and many people like myself have done it
within a Desktop X terminal window, for many years, quickly and routinely.
For 6.0.2, xserver is upgraded for the first time in a long time.
If users are desktop users, and don't realize what has happened,
the X restart could take them by surprise and they don't end up
truly upgrading all packages. I can imagine this confusing
some users.

Personally, I don't want to close out all my Xsession windows each time
I do aptitude safe-upgrade, and I will continue to run it within X,
unless I see another case like 6.0.2 where part of X is getting
updated.

6.0.2 safe-upgrade was atypical, and thus the purpose of the post.

Relevant Pages

  • Re: Problems Upgrading Image from SP1 to SP2
    ... Suprisingly the auto login still works after the SP2 upgrade... ... Configuration -> Upgrade Component. ... Automatic Logon is no longer working for the administrator account. ...
    (microsoft.public.windowsxp.embedded)
  • RE: Old NT Domain Name Still Present at Login After Upgrading to 2003 Domain
    ... when you perform an in-place upgrade from NT4 to windows ... system will ask you to input netbios domain name & dns domain ... domain name is different from dns domain name. ... Old NT Domain Name Still Present at Login After Upgrading to ...
    (microsoft.public.windows.server.migration)
  • Re: workstations have problem with login after upgrading nt4 to w2k with AD and DNS
    ... It seems that the first login after the ... upgrade for each client is when the domain information is aquired from the ... > I put in my Windows 2000 server CD and choose the upgrade option. ... > For the DNS name for the network, ...
    (microsoft.public.windows.server.migration)
  • Re: WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 from NT4.0)
    ... Original PDC is in the production NW ... When you take TBDC offline and upgrade it to PDC, can all clients login ... WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 ...
    (microsoft.public.windows.server.migration)
  • Re: More X Problems Today
    ... I use kdm as my login display manager. ... should avoid installing packages or dependencies which are broken. ... FWIW the xorg upgrade is 'held' here without any intervention from me. ...
    (Debian-User)