[pca] why does PCA install 113859 on a S10u6 system

[Don O'Malley]

Hi Karl,

It looks like you have some of the Directory Server pkgs on your system.

Can you confirm this by doing a 'pkginfo | grep IPLT'
You should see something like this:

root at anteater # pkginfo | grep IPLT
system      IPLTadcon                        Administration Server Console
system      IPLTadman                        Administration Server Documentation
system      IPLTadmin                        Administration Server
system      IPLTcons                         Console Client Base
system      IPLTdscon                        Directory Server Console
system      IPLTdsman                        Directory Server Documentation
system      IPLTdsr                          Directory Server (root)
system      IPLTdsu                          Directory Server (usr)
system      IPLTjss                          Network Security Services for Java
system      IPLTnls                          Nationalization Languages and Localization Support
system      IPLTnspr                         Portable Runtime Interface
system      IPLTnss                          Network Security Services
system      IPLTpldap                        PerLDAP
root at anteater #


So, where have these pkgs come from?

These pkgs are included with the Solaris 10 image for customers who are 
upgrading from Solaris 9 to Solaris 10.
See http://docs.sun.com/app/docs/doc/817-0552/6mgbi4fgr?a=view for 
further details.

I would think that you have ended up with these pkg on your system either:
* As a result of upgrading the system from Solaris 9
* As a result of the manner in which you installed your machine (i.e. 
adding the pkg from jumpstart or similar)
* By manually adding the pkgs to your machine at some stage.

Note: These pkgs will not be installed by default onto a Solaris 10 
system, as they are not listed in any of the install clusters - i.e. 
Looking at the .clustertoc file in the Solaris 10 U6 image:
#  grep IPLT 
/export/images/SPARC/solaris_10_u6/Solaris_10/Product/.clustertoc
#

(Compared with the Solaris 9 image, where these pkg do get installed as 
part of an install cluster:
# grep IPLT /export/images/SPARC/solaris_9_u8/Solaris_9/Product/.clustertoc
CLUSTER=IPLTCids
SUNW_CSRMEMBER=IPLTadcon
SUNW_CSRMEMBER=IPLTadman
SUNW_CSRMEMBER=IPLTadmin
SUNW_CSRMEMBER=IPLTcons
SUNW_CSRMEMBER=IPLTdscon
SUNW_CSRMEMBER=IPLTdsman
SUNW_CSRMEMBER=IPLTdsr
SUNW_CSRMEMBER=IPLTdsu
SUNW_CSRMEMBER=IPLTjss
SUNW_CSRMEMBER=IPLTnls
SUNW_CSRMEMBER=IPLTnss
SUNW_CSRMEMBER=IPLTnspr
SUNW_CSRMEMBER=IPLTpldap
SUNW_CSRMEMBER=IPLTCids
SUNW_CSRMEMBER=IPLTCids
#

Bottom line is that it is harmless to have these pkgs applied to a 
Solaris 10 system and they are primarily for customers upgrading from 
Solaris 9 (hence the reason why the Synopsis for patch 113859-04 is 
"SunOS 5.9: Sun ONE Directory Server 5.1 patch").

I hope this sheds some light on the issue for you.

Best,
-Don

Karl Rossing wrote:
> I have a Solaris 10u6 server. When I do a pca -i missing PCA wants to 
> install:
> 113859 -- < 04 RS- 999 SunOS 5.9: Sun ONE Directory Server 5.1 patch
>
> patchdiag.xref from Feb/02/09
> -bash-3.00$ uname -a
> SunOS server2 5.10 Generic_137137-09 sun4u sparc SUNW,Sun-Fire-V240
> -bash-3.00$ pca -v
> pca 20081218-01
> -bash-3.00$ cat /etc/release
>                      Solaris 10 10/08 s10s_u6wos_07b SPARC
>           Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.
>                        Use is subject to license terms.
>                            Assembled 27 October 2008
>
> Thanks
> Karl
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE:  This communication (including all 
> attachments) is
> confidential and is intended for the use of the named addressee(s) 
> only and
> may contain information that is private, confidential, privileged, and
> exempt from disclosure under law.  All rights to privilege are expressly
> claimed and reserved and are not waived.  Any use, dissemination,
> distribution, copying or disclosure of this message and any 
> attachments, in
> whole or in part, by anyone other than the intended recipient(s) is 
> strictly
> prohibited.  If you have received this communication in error, please 
> notify
> the sender immediately, delete this communication from all data storage
> devices and destroy all hard copies.
>