Hi Dave,

> I am willing to do the update, but I want to confirm the procedure
> before I touch anything.

Thanks!

> My assumptions:
>
> The image to be updated is /srv/sourcesqueakorg/box4/squeaksource/webserver/ss.image,
> and a backup copy of the current ss.image/changes should be saved.

Yes.  The image is saved with nothing running, just the code base
installed.  The server is started via .st script.

> The image can be updated off line by copying to my local system, applying
> the patch, and copying back to the server.

Yes.  If you want to get your MCConfigurations enhancement in, it will
need to be able to run in Squeak 5.2 for now.

> Restarting the source.squeak.org image will restart it using the updated ss.image.
>
> Clean shutdown should be done with sudo svc -d /service/squeaksource.
>
> Startup is done with sudo svc -u /service/squeaksource.

Yup.

> The supervise script will restart the image, starting with ss.image and
> loading everything back from the Magma backing store.

Yes.

> If anything goes wrong with the above steps, I can restore the saved
> ss.image, restart it, and all would be well.

Yes, and I'm sure imply that you would do svc -d during that so
doesn't keep trying to restart it in uncontrolled fashion while you're
switching the image back.

> Does that sound right? If so I will plan to do the update tomorrow.
>
> With your permission, I will also apply an update to MonticelloConfigurations
> to enable versioning of MCM maps.

Sure, thanks.  As long as you're willing to support it if there's a
problem, go for it.  :)   It sounds like you definitely have a good
handle on the system, so I'm confident.

> Also, if there is a VNC connection available for either the image or
> for the dan.box.squeak.org server, I would feel more comfortable if you
> can tell me how to open that connection.

I'll send these details in a separate email.

Thanks, glad to have a backup for source.squeak.org.

 - Chris