The Real Warren Belfer wrote:
EndaO'Connor wrote:

The Real Warren Belfer wrote:

Phil Freund wrote:

119254-32 contains a fix that is vital to patching in single user mode with zones ( that is zones that are halted ) it is necessary to install this patch in Multi User Mode ( actually patch does not specify any dependency on Single user Mode ) But I will clarify this in a patch README note in 119254/119255-36 which will b e released in the coming days

In general the patch README specifiies if the patch is reboot immediate, reboot required etc.


Thanks Edna, that helps a lot. But most folks apply patches in bulk,
and if one, like the Kernel patch requires single user, then typically
they all get installed in single user. I have never heard of anyone
breaking up the Rec and Sec cluster into pieces that may be installed
in multi user versus those that cannot.

It seems to me that if a patch _must_ be installed in multi-user, that
fact should be flagged in big letters at the top of the patch README.

I would still like to know if there are any resources that explain
patching systems with zones - or should it just work no matter how
we do it ? :-)


Hi Warren
One option is to boot the system ( global zone ) to single user mode ( SUM ) and then boot eh zones to SUM as well.
so boot global zone to SUM, then
 #zoneadm -z <zone-name> boot -s
for each zone.

then apply the cluser, once 119254-32 or greater is installed, Single User Mode should all just work going forward after that.

basially a zones need to be booted at least once in order for patchadd to work,
so say you run
#zoneadm -z zone-test install
#patchadd 118833-36
this will fail, you must boot the zone at least once before patching, in order to set up the zones device tree etc. Remember that the although the zone will show as "running" sysidtool and svc etc all need to run after this. if booting a zone for the first time prior to patching, best to zlogin -C to determine of zone setup has finished.

zones in a state of "configured" can just be patched as is.

zones-discuss mailing list

zones-discuss mailing list

Reply via email to