by Well, I normally reinstall from scratch, but in the case of upgradesQuote:> Hello,
> How have you admins been handling the upgrade of systems from 2.5.1 to
> 2.6. Back when we created these systems (30 in total), there was only
> 2.5.1 and patches. The filesystem layout required a 250Mb /usr. Now
> when I go to upgrade to 2.6, /usr wants at minimum 432, 650MB ideal
> and our few 2.6 systems are using more like 425MB each.
> So short of redoing or swapping filesystem partitions for each and
> every machine, is there some way to upgrade to 2.6 and either:
> 1. install a lot less into /usr and still have full functionality
> 2. install the excess or other stuff in /usr to some other directory
> with more space and if so, which packages are space hogs yet not so
> essential?
you'll probably find that moving /usr/openwin into a separate partition
would be sufficient. On one of our machines:
/dev/dsk/c0t3d0s6 218679 161888 56573 75% /usr
/dev/dsk/c0t1d0s7 288391 91405 196698 32% /usr/openwin
and that's a fully functional install (essentially SUNWCprog less man
pages and some sample code, but well tuned beyond that). Originally it
was running 2.4 with just /usr, I just moved /usr/openwin onto a
separate disk and then did the upgrade to 2.6.
(Mind you, a reasonable chunk of /usr is actually taken up by the
Solstice Backup client.)
If you're ever going to run Solaris 7 in 64-bit mode, you're going to
need a lot more space again.
What are the machines used for? You may not need the SUNWCkcms,Quote:> Are there any lists of what I can just not install or skip?
SUNWCutf8, or SUNWCdtdev clusters. You may not need the man pages on
every single host. The static lint binaries (SUNWxwslb and SUNWolslb)
and the sample source code don't need to be on every machine, and you
may be able to live without the demo images (SUNWxwdim).
--
-Peter Tribble
HGMP Computing Services
http://www.hgmp.mrc.ac.uk/~ptribble/