On 08/05/09 17:15, Jacqueline Tse wrote:
so from within a non-global zone
1 if /var/sadm/pkg/<pkg-name>/pkginfo has
SUNW_PKG_ALLZONES-true then can only be managed from global,
else if false then check that no entry in
/var/sadm/install/contents for this package lives on an inherited filesystem.

On GZ and NGZ, /var/sadm/pkg/ABCDtestpkg/pkginfo has no info regarding SUNW_PKG_ALLZONES.
so is if then false by default, so need to then test if any parts live on an inherited dir inthe NGZ.

ABCDtestpkg lives in /opt, not on an inherited filesystem. I thought the NGZ 
does not know it's filesystem is inherited or not?!

well one could check the NGZ's /etc/mnttab
# grep /usr /etc/mnttab
/usr    /usr    lofs    ro,nodevices,nosub,dev=1d80008  1248987336
so clearly read only /usr in this NGZ, then if any bits of the package live in /usr it cannot be managed from the NGZ.

/var/sadm/install/contents is a flatfile maintained
by patch/packaging tools. grep for say SUNWcsr and you will see the
structure, or man -s 4 contents.

The info about ABCDtestpkg in /var/sadm/install/contents is the same in GZ and NGZ.
yes, but at least you can see if bits of said package live on an inherited dir or not. If they don't and pkginfo has ALLZONES=false or not set at all, then package can be managed from the NGZ.


Still a bit unclear as to the use of this tool, by
run in the global and/or non0-global zone, you mean they can be managed
ie patched/removed etc?

The tool is used to report packages that are installed on the GZ and NGZ, which will be 
run in GZ and NGZ. When a package "ABCDtestpkg" is installed in the GZ, and 
duplicated into all NGZ, the tool running on the NGZ must not report the duplicated 
version of ABCDtestpkg. This is to avoid multiple count of the same  package.

Enda O'Connor x19781  Software Product Engineering
Patch System Test : Ireland : x19781/353-1-8199718
zones-discuss mailing list

Reply via email to