Re: [zones-discuss] Patching for zones with own /usr
Jeff Victor wrote: See http://docs.sun.com/app/docs/doc/817-1592/6mhahuoog?a=view for some more info. Hmm ... this does not admonish that you should not use zero i-p-d or all four. I agree with Steffen that if this leads to an unsupported environment the customer should at least get a warning in the doc. I would say I'm fairly familiar with zones and this is news to me. I realize we can't itemize everything that may lead to an unsupported system (how would we know?) but my interpretation of the doc is that we make it easy for the customers to use a -b template or a default template, but they can pick and chose. I hope this is not unsupported, if I were a customer and I found this out through a service call I would be a little aggravated. Regarding the other customer's question about a zone with all four + /opt i-p-d, I believe their intention was to patchadd -G in each zone that requires it. CT ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
Mike Gerdts wrote: On 3/15/07, Jeff Victor <[EMAIL PROTECTED]> wrote: Inheriting 1, 2, or 3 of these dir's isn't called anything, and very little, if any, testing has been done to see what happens with those. See http://docs.sun.com/app/docs/doc/817-1592/6mhahuoog?a=view for some more info. Huh? I've been using zones since before Sun was shipping Solaris 10 CD's, with various combinations of inherit-pkg-dir and have followed zones-discuss regularly for a very long time. This is the first that I have heard anyone mention that only SUNWdefault SUNWblank are the supported configurations. If that is the case, why on earth does inherit-pkg-dir exist in the zonecfg man page? I see nothing about the supportability of alternate inherit-pkg-dir selections listed in the page above. I have patched in between setups, basically patchadd ( and ti's friends ) do not have any hard coding on whole vs sparse, they simply determine what dirs are inherited and pass them down the stack, the underlying tools then work on that basic. So having 3 inherited dirs is quite ok, The OP's questions regarding the -G option suggests that the global zone may have been patched with patchadd -G, which would result in confusing configurations with the various non-global zones. Perhaps patchrm and patchadd (sans -G) would be in order. was patchadd -G used or not as I'm not too clear? Enda Mike ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
Jeff Victor wrote On 03/15/07 20:31,: Mike Gerdts wrote: On 3/15/07, Jeff Victor <[EMAIL PROTECTED]> wrote: Inheriting 1, 2, or 3 of these dir's isn't called anything, and very little, if any, testing has been done to see what happens with those. See http://docs.sun.com/app/docs/doc/817-1592/6mhahuoog?a=view for some more info. Huh? I've been using zones since before Sun was shipping Solaris 10 CD's, with various combinations of inherit-pkg-dir and have followed zones-discuss regularly for a very long time. This is the first that I have heard anyone mention that only SUNWdefault SUNWblank are the supported configurations. If that is the case, why on earth does inherit-pkg-dir exist in the zonecfg man page? I see nothing about the supportability of alternate inherit-pkg-dir selections listed in the page above. Sorry Mike, and anyone else confused by my brevity. I'll try to be clearer by being even briefer: ;-) Good: "sparse-root + inherit-pkg-dir of anything except /usr, /lib, /sbin or /platform" Good: "whole-root + inherit-pkg-dir of anything" Bad: "sparse-root + inherit-pkg-dir of /usr, /lib, /sbin and/or /platform" That was the "Inheriting 1, 2 or 3..." part. Did that help? I made the same statement you are making (either inherit all four or inherit none) to a customer during a presentation today, and said to myself "self, if that is all we support/recommend, why do we not make sure that one of those two is verified during the config or install?". Although I said those are the two, looking at the doc you referenced, it does not say you must only inherit all four or none, that partial configurations are not allowed. The strongest word I see is 'default'. I understand the reasoning for only supporting two configuration options instead of all 16. Maybe it needs to be stated more clearly and enforced. Steffen reply-to set to aliases ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
Mike Gerdts wrote: On 3/15/07, Jeff Victor <[EMAIL PROTECTED]> wrote: Inheriting 1, 2, or 3 of these dir's isn't called anything, and very little, if any, testing has been done to see what happens with those. See http://docs.sun.com/app/docs/doc/817-1592/6mhahuoog?a=view for some more info. Huh? I've been using zones since before Sun was shipping Solaris 10 CD's, with various combinations of inherit-pkg-dir and have followed zones-discuss regularly for a very long time. This is the first that I have heard anyone mention that only SUNWdefault SUNWblank are the supported configurations. If that is the case, why on earth does inherit-pkg-dir exist in the zonecfg man page? I see nothing about the supportability of alternate inherit-pkg-dir selections listed in the page above. Sorry Mike, and anyone else confused by my brevity. I'll try to be clearer by being even briefer: ;-) Good: "sparse-root + inherit-pkg-dir of anything except /usr, /lib, /sbin or /platform" Good: "whole-root + inherit-pkg-dir of anything" Bad: "sparse-root + inherit-pkg-dir of /usr, /lib, /sbin and/or /platform" That was the "Inheriting 1, 2 or 3..." part. Did that help? -- -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
On 3/15/07, Jeff Victor <[EMAIL PROTECTED]> wrote: Inheriting 1, 2, or 3 of these dir's isn't called anything, and very little, if any, testing has been done to see what happens with those. See http://docs.sun.com/app/docs/doc/817-1592/6mhahuoog?a=view for some more info. Huh? I've been using zones since before Sun was shipping Solaris 10 CD's, with various combinations of inherit-pkg-dir and have followed zones-discuss regularly for a very long time. This is the first that I have heard anyone mention that only SUNWdefault SUNWblank are the supported configurations. If that is the case, why on earth does inherit-pkg-dir exist in the zonecfg man page? I see nothing about the supportability of alternate inherit-pkg-dir selections listed in the page above. The OP's questions regarding the -G option suggests that the global zone may have been patched with patchadd -G, which would result in confusing configurations with the various non-global zones. Perhaps patchrm and patchadd (sans -G) would be in order. Mike -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
Christine Tran wrote: Jeff Victor wrote: Customer has zones with 3 out of 4 default inherit-pkg-dir, each zone has its own /usr. They are reporting that a DST patch did not install correctly in the non-global zone. Was that "3 out of 4 zones has all the default i-p-d's" or "the zones have 3 out of the 4 default i-p-d's" ?? If the latter, the answer is "that's not supported, and the results are not well understood." The latter. I seem to have missed this email thread, can you tell me about the "not supported, not well understood" part? Trim the alias if it's been discussed to death, or just point me to a link. Thanks! Hmmm... I don't recall when this topic was last discussed, but all supported zone config's are either "sparse-root" (the default, which means "inherit /usr, /lib, /platform, /sbin") and "whole-root" (don't inherit any of those four). Inheriting 1, 2, or 3 of these dir's isn't called anything, and very little, if any, testing has been done to see what happens with those. See http://docs.sun.com/app/docs/doc/817-1592/6mhahuoog?a=view for some more info. -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
Jeff Victor wrote: Customer has zones with 3 out of 4 default inherit-pkg-dir, each zone has its own /usr. They are reporting that a DST patch did not install correctly in the non-global zone. Was that "3 out of 4 zones has all the default i-p-d's" or "the zones have 3 out of the 4 default i-p-d's" ?? If the latter, the answer is "that's not supported, and the results are not well understood." The latter. I seem to have missed this email thread, can you tell me about the "not supported, not well understood" part? Trim the alias if it's been discussed to death, or just point me to a link. Thanks! CT ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Patching for zones with own /usr
Christine Tran wrote: Hi, Customer has zones with 3 out of 4 default inherit-pkg-dir, each zone has its own /usr. They are reporting that a DST patch did not install correctly in the non-global zone. Was that "3 out of 4 zones has all the default i-p-d's" or "the zones have 3 out of the 4 default i-p-d's" ?? If the latter, the answer is "that's not supported, and the results are not well understood." Perhaps related to this, last week I had another question about patching a zone which had an /opt inherit-pkg-dir. Assuming that SUNW_PKG_ALL_ZONES is false, if part of a package is installed in /opt, and part is installed in the zone's copy of /var, what should I do to install or patch? If I use pkgadd -G in the global zone, it only installs in the global zone. If I use pkgadd -G in the non-global zone, it can't write to /opt. Assuming that you want to install it in all zones: Did "pkgadd without -G" in the global zone not work? That's what I would have done. -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Patching for zones with own /usr
Hi, Customer has zones with 3 out of 4 default inherit-pkg-dir, each zone has its own /usr. They are reporting that a DST patch did not install correctly in the non-global zone. Perhaps related to this, last week I had another question about patching a zone which had an /opt inherit-pkg-dir. Assuming that SUNW_PKG_ALL_ZONES is false, if part of a package is installed in /opt, and part is installed in the zone's copy of /var, what should I do to install or patch? If I use pkgadd -G in the global zone, it only installs in the global zone. If I use pkgadd -G in the non-global zone, it can't write to /opt. CT ___ zones-discuss mailing list zones-discuss@opensolaris.org
