upgrading Gutsy to Hardy, remotely .... advice and precautions?

[NoOp]

On 11/28/2008 09:42 PM, H.S. wrote:
> NoOp wrote:
> 
>> 
>> Actually a good question.
>> 
>> Shouldn't be a problem. However, you'll lose him when the system
>> reboots. I recommend trying it on a local test system first; if you
>> don't have one, I do and can it a try tonight or tomorrow if you'd like.
> 
> It would be nice ... but I wouldn't want to trouble you with all this
> hassle. However, if you have time to try it out, it would be great.
> 
> What I am expecting is this:
> - pop in the laternate CD while the user is logged in and is in adm
> group (admin privileges)
> - start the upgrade using the steps in the URL I mentioned earlier
> - the upgrade should proceed with some possible package removals. Need
> to jot this down in a text file - remote desktop is running so I can do
> that.
> - At the end, a reboot will be required. The PC has a fixed IP address
> in his home. The DSL connection is made by his modem. So the reboot
> should not be a problem. The PC is going to get the same address and it
> doesn't mess with the ADSL connection.

After he inserts the CD & starts the process, he can select the option
to upgrade directly from the CD; that way he does the bulk upgrade from
the CD only, and then after reboot he can connect and download the
updates. That will cut the install time by about an hour. Note: I
generally disconnect the network when I do this, but obviously you won't
want to do this if you are monitoring remotely.
  If you select the option to use the network, the downloads via a
standard 1.5Mbps DSL will take about 1.5 hours, install/upgrade configs
about another 1.5 hours. The biggest issue from your side will be that
you'll need to monitor the upgrade questions towards the latter part of
the upgrade. Unfortunately it's not an unattended upgrade because it
will ask if you want to use your existing grub, cups, etc., configs or
replace with the new defaults. My recommendation is to keep your existing.

> - Then talk him to setup the remote desktop again in case it does not
> function.

If he runs into desktop issues you'll not likely be able to talk to his
system via remote. SSH perhaps, but most likely not via remote desktop.
So, I'd make sure that ssh is installed and working before you start.
Test by logging in using the -X command:
ssh -X <hisusername>@<hisIPaddress>
Then while connected via ssh, make sure that you can open his remote
desktop preferences:

$ vino-preferences

That will bring up (on your side) the same as if you were to
System|Preferences|Remote Desktop at his desktop.

Note: you will not be able to do any -X functions if his desktop is
borked, but if networking & ssh is working you'd still be able to use
the standard terminal to try and fix the issue.

> - Then install the packages that were earlier removed and update the system.