Well, if this patch need to be installed in all zones otherwise it will make system inconsistent then it is Global! If it touch shared area one way or another and all Kernel Utility patches touching Kernel which are shared over tones - then this patch is Global! Global mark is needed to switch pdo behavior one way or another and this is only defenition of Global patch - so pdo should handle it this way, then it must be marked Global, otherwise not.
If it is marked as a Global and pdo is not installing it - then it is an error in pdo. If it is not marked as a Global - then pdo doing what it is suppose to do with non Global patches. Now if it is not Global patch and in some zones it can not be installed because some dependencies are not resolved (otherwise it will break zone) - then pdo installing it on all zones where it is OK to install it and report where it can not install it and why. This is what pdo doing here in this case - telling you on which zones it can not be installed and why. psc-201n: For patch 120272-13, required patch 118833-36 does not exist. eule-201n: For patch 120272-13, required patch 118833-36 does not exist. kops-201n: For patch 120272-13, required patch 118833-36 does not exist. kops-227n: For patch 120272-13, required patch 118833-36 does not exist. lsorui-218n: For patch 120272-13, required patch 118833-36 does not exist. Pdo was smart enough to skip already installed patches from the time it was introduced - Solaris 10 FCS 2005. If you check pdo explanation thread in this forum you may see details. In short pdo create dependency tree for all patches requested to install and installed and do some math - complete tree analysis to recognize all patches needed to be installed or patches which can not be installed or patches which no need to install. It doing it for all zones and produce lists of patches to install for each. Because of this it can handle multyple patches specified in any order, patch directory etc... Thanks, Vassili. This message posted from opensolaris.org
