>Sun told our IT Services people that the SC2000 they ise *had* to be
>reinstalled rather than upgraded, if memory serves correctly.
I've been haranguing (sp?) on this subject forever. Aug 4-5 was our
re-install. There are about six fatal problems with the upgrade, and
most large machines (690 and above) fall victim to them. My unscientific
survey yielded one claim of success on large machines, to about twelve
nays. It can be done, I guess, but you've got to be lucky.
For another thing, everybody acts like re-installing is trivial.
It is far from it. Oh, sure, it is for a small machine, but let's
remember, I have two SSAs, prestoserve, 10 total tape drives, 1.5 GB
mem, wide and narrow differential scsi controllers, two fddi interfaces,
and so on. You don't just "re-install". You lose all of your NIS, DNS,
syslog, inittab, etc/system, /etc/*.conf configurations. You lose all
your mount points in /, /etc/vfstab, and so on. Think /etc/vfstab is
simple? If you have a trivial SS10, I'll bet. But remember, I have to
restore /etc/vfstab in stages -- because the SSA software isn't automatically
there. Furthermore, because we wish to share X with other machines, and
because we want all of our shared material to be on the file server,
the SUNWits package will be put into /opt by the re-install, but will
have to be deleted and re-installed AFTER the networking is restored
else you'll have inconsistencies in /var/sadm/install/contents.
There's about ten other things like this in a large installation.
If the upgrade would work, it should be able to do a pkgchk and
determine that xgl and xil are not in /opt, they're in /opt/depot.
But the upgrade won't play ball, because /opt/depot is partly on
an SSA -- which the upgrade can't operate.
sorry. the upgrade is a hot button for me....
j.
--
Jay Scott 512-835-3553
Applied Research Labs, Computer Science Div.
University of Texas at Austin