<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Courier New" size="2"><span style="font-size:10pt;">
<div>Martin Paul wrote:</div>
<div>> Not me. I have only minimal experience with patch zones (and zones in general).</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div> No worries, thanks Martin. Many zones users prefer to detach them before patching, and then use “zoneadm attach –u” (Update on Attach) afterwards to speed up the patch process. I left this particular full-root zone attached, and let patchadd handle
it directly.</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div> I spun another crackpot theory: When patchadd calls zone_enter(), the existing $TMPDIR (relative to GZ root) carries over, and does reflect the chroot()ed zonepath. In other words, package tools in the NGZ try to access a temporary directory accessible
only in the GZ.</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div> That may not even be technically possible, but I’ve seen stranger things before, and I’m admittedly short of ideas. =-) Perhaps some other readers have run into this… Anyways, I agree that my syndrome doesn’t look quite the same as the EUID nobody
issue. Thx… -c</div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
</span></font>
</body>
</html>