Re: Is S10U3 + patch-cluster = S10U4?
- From: James Carlson <james.d.carlson@xxxxxxx>
- Date: 20 Dec 2007 15:56:30 -0500
Rainer Duffner <rainer@xxxxxxxxxxxxxxx> writes:
James Carlson wrote:
Rainer Duffner <rainer@xxxxxxxxxxxxxxx> writes:
this seems a silly question, but if I install from the Solaris 10U3 DVD
and apply the latest patch-cluster, is it then "Solaris 10U4"?
No.
Or how else do I upgrade?
There are at least two ways to do this. Both start with getting the
S10U4 distribution medium -- the DVD -- from Sun.
You next:
- Boot the S10U4 DVD and select "upgrade" from the menus. This
requires that your system is down while the upgrade occurs.
- Use the Live Upgrade feature to copy the current boot environment
to a spare disk slice, upgrade that copy without taking the system
down, and then switch over to the upgraded system.
OK, thanks a lot (also to the other posters).
So this means that I have to make special provisions at install-time, so
I can "clone" the boot-slice, right?
Yes. Note that I said "boot environment." That includes the slice
containing the root file system, plus any non-shared file systems.
See the LU documentation for more details.
What is the boot-slice anyway?
Root (/).
Solaris seems to install lot's of stuff in lots of places (/, /usr/,
/var and /opt, according to this
http://www.sun.com/bigadmin/features/articles/live_upgrade.html 2004-ish
article - is that still true?
Yes.
You need to make sure that the places where Solaris installs bits are
_not_ shared between boot environments.
Of course, you can mount shared things underneath there, provided
you're careful. It's fairly common to have a common mount point for
/opt/csw (blastwave bits) or /var/crash (for crash dumps), and have
the file system mounted in each case being shared between boot
environments.
The caveat is that the System V packaging database is always unshared
between boot environments -- that's how Live Upgrade is able to work;
it works on an unshared copy. The implication of this is that if you
have packages installed on a shared file system (such as /opt/csw),
you have to be sure that you don't modify the packages in one
environment and then try to access them in another.
A reasonable procedure looks like:
- upgrade all non-Sun bits
- use lumake or lucreate to copy Solaris to a new BE
- upgrade the new BE with luupgrade or patchadd
- luactivate and init 6 to switch over
- continue using the system normally
(Yes, the installed Solaris bits in /opt are a pain. I hope that
future versions deal with this better.)
--
James Carlson, Solaris Networking <james.d.carlson@xxxxxxx>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
.
- References:
- Is S10U3 + patch-cluster = S10U4?
- From: Rainer Duffner
- Re: Is S10U3 + patch-cluster = S10U4?
- From: James Carlson
- Re: Is S10U3 + patch-cluster = S10U4?
- From: Rainer Duffner
- Is S10U3 + patch-cluster = S10U4?
- Prev by Date: Re: solaris build error ... help needed
- Next by Date: Re: Can't log into remote desktop XDMCP
- Previous by thread: Re: Is S10U3 + patch-cluster = S10U4?
- Next by thread: How to find out Global Zone's ip from Local Zone??
- Index(es):
Relevant Pages
|
