4.0.3 upgrade script gotcha

[Ruth Milner]

If you are running a homogeneous server with Sunlink installed, you may
run into a problem during the upgrade from 4.0[.1] to 4.0.3.

If your setup is such that the clients' executables are located in /usr
(i.e. shared with the server as is the usual setup for a homogeneous
server), and you have Sunlink DNI or possibly other Sunlink products
installed in the usual location under /usr/sunlink, your upgrade will get
partway through and then say "Upgrading sunlink clients".

The problem is in the script /usr/etc/upgrade/get_clientinfo. It does an
ls in the path for client executables (i.e. /usr), greps for "sun", and
then grep -v's for a select group of names which it doesn't want to touch.
These include "sunos4", "sun3x", and "sun4c". It should also include
"sunlink".  To fix, after booting the 4.0.3 tape miniroot but before
running sunupgrade, edit the get_clientinfo script so that the lines which
contain something like this (this is not exact, sorry):

ls ${CLIENTEXEC} | grep sun | grep -v sunos4 | grep -v sun4c ... etc.

also includes a pipe to grep -v sunlink. Then run sunupgrade. Apologies
for not having made a note of the exact contents of the line, but it is a
very short script (~60 lines) and this will be very easy to find.

This bug has been reported to our local Sun office and is being passed on
to California (which may already know about it).

If you have any local directories in /usr with "sun" in the name, you will
also want to grep -v for those.

Overall the 4.0.3 upgrade was pretty smooth. Note that if you have made
modifications to /usr/sys/sun{x}/conf/files, this is one of the few the
ugprade script does not save. Save it yourself and put your modifications
in the new version (which has other differences).

Ruth Milner
Systems Manager
University of Toronto Physics