Very Computer

        The upgrade cdrom never discovers a bootable Solaris 2.3
disk, even though it's there.  In fact, it's the internal disk:
c0t3.  Not being able to find a way around this, I gave up.
[Basically, I never get to click on the upgrade option button -
 it's never presented. grrrrrr!]

        I'd rather not install a "new" Solaris 2.4 system and then
reconfigure everything.  Has anyone encountered this problem before?
If so, how did you solve it?  Thanks in advance for any advice or
suggestions.

Here's my environment:

Hardware: SS20, 4 processor, 512 MB RAM. 2 internal disks, / /usr on
one, /opt on the other.  swap space on both of them.

Software: Solaris 2.3.  Sun compilers.  SUNWnskit (YP for Solaris 2.X),
recommended Solaris 2.3 patches.  This machine is the NIS master,
main fileserver and mail gateway.

Ric Steinberger
Software Engineer

"We figured it 17 different ways, and every way we figured it, somebody
 didn't like the way we figured it!"   Buddy Hackett
                                       It's a Mad Mad Mad Mad World

A number of people have moved /var/sadm/ to a different partition because
of the size of the installed patches and made a symlink.  That will work,
but you must make sure that the symlink is relative (../big/fs/sadm), not
absolute (-> /big/fs/sadm)
All the filesystems are mounted under /a and then the system tries to access
/a/var/sadm/softinfo, which breaks in the presence of absolute links.

If you haev a disk > 2GB, you'll have to do thinks differently as well.
If they don't contain 2.3 data, you can just comment the entries in /etc/vfstab
out.  We've also seen it core dump, which can be fixed by removing patches
so that all lines in /var/sadm/install/contents are < 1024 chars.

Casper
--
Casper Dik - Network Security Engineer - Sun Microsystems
This article is posted from my guest account at the University

Opinions expressed here are mine (but you're welcome to share them with me)