Many thanks. The papers in the link from James Carlson provide valuable insight into the Live Upgrade process, especially relating to issues we have been experiencing with upgrading non-global zones.
Sincerely Rob McDonald -----Original Message----- From: James Carlson [mailto:james.d.carl...@sun.com] Sent: Thu 2/5/2009 05:23 PM To: Dr. Hung-Sheng Tsao (LaoTsao) Cc: Rob McDonald; email@example.com Subject: Re: [zones-discuss] Scratch Zone - purpose Dr. Hung-Sheng Tsao (LaoTsao) writes: > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6328286 > > Rob McDonald wrote: > > > > Hi All > > > > Can anyone explain what a scratch zone is or point me to a relevant > > document? In addition to the above CR, see: http://www.opensolaris.org/os/community/arc/caselog/2005/474/ A "scratch zone" is a mechanism that allows us to mount up a zone that exists in an alternate boot environment (a separate system root). The zone can't be booted (it's not known whether all of the bits, including configuration, inside are runnable on the current kernel), but it's possible to make processes enter the zone, and common directories (such as /usr and /lib) have lofs mounts from the running system to allow some limited work to be done. Scratch zones are used as part of the upgrade process. They're intentionally undocumented, because they're meant to be an internal design detail. -- James Carlson, Solaris Networking <james.d.carl...@sun.com> 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
_______________________________________________ zones-discuss mailing list firstname.lastname@example.org