Xun Ni: You should use pkg image-update to update your DC build machines and not onu. onu only update ON packages and it will not update your DC and install packages required to do the builds since it comes from solaris repo.
Also as Niall had point out in the flag date, you need to copy over the new DC build template and customize it with the facet.blog. You cannot use build 9 DC template to do build on build 13. ----- Original Message ----- From: [email protected] To: [email protected] Cc: [email protected], [email protected], [email protected], [email protected] Sent: Thursday, April 19, 2012 7:45:21 AM GMT -08:00 Tijuana / Baja California Subject: Re: [caiman-discuss] Need help on the DC Hi, Niall: Thanks for your reply on my question. You can't access the /root because you didn't login as root(l1admin). we onu the system to our workspace but still get the same error. you can check on that machine for detail. watergrass.cn.oracle.com(root/l1admin) Thanks, Xun > Hi Xun, > > I had a look on your system. None of the files below under /root are > readable. > I did have a look at the original log of the last DC build on your > system here: > > /rpool/dc/text/logs/detail-log.2012-04-20.08:44 > > Your problem is that your DC build system is too old - it looks like > s11u1_09: > > -bash-4.1$ pkg info core-os > Name: system/core-os > Summary: Core Solaris > Description: Operating system core utilities, daemons, and > configuration > files. > Category: System/Core > State: Installed > Publisher: on-nightly > Version: 0.5.11 > Build Release: 5.11 > Branch: 0.175.1.0.0.9.18558 > Packaging Date: March 30, 2012 09:19:29 AM > Size: 15.91 MB > FMRI: > pkg://on-nightly/system/[email protected],5.11-0.175.1.0.0.9.18558:20120330T091929Z > > > > To build ISO images that include the latest on-nightly (or the Solaris > dev repo version 14 or above) publishers, > you must be running s11u1_13 at a minimum due to satisfy GRUB2 > dependencies on the build system. > > The flag days are here: > http://on11update-gate.us.oracle.com/flagdays/pages/20120324070404.html > http://on11update-gate.us.oracle.com/flagdays/pages/20120330034248.html > > Thanks, > Niall > > On 04/19/12 06:54 PM, xunni wrote: >> Hi, Mary: >> >> I have changed the xml file with your comments and it still not >> work. can you take some time to have a look? >> >> machine: watergrass.cn.oracle.com >> xml file: /root/dc_text_x86.xml >> /root/lang_facets.xml >> log file: /root/detail-log.2012-04-20.06:08 >> >> Thanks, >> Xun >>> Xunni: >>> >>> Since you use the on-nightly, you will need to modify your xml as >>> follow to unconstrain the osnet-incorporation in order for the build >>> to work. >>> >>> >>> Please look at the attachment about using facet to do this for DC >>> builds. I will suggest you also upgrade your DC build machine >>> following Niall Power flag date due to the grub2/uefi changes that >>> comes in. >>> >>> >>> >>> >>> On 04/18/12 02:02 AM, xunni wrote: >>>> Hi, Mary: >>>> >>>> Recently the nightly result has changed: >>>> >>>> it was: packages/i386/nightly-nd/repo.redist repo.extra >>>> now: packages/i386/nightly-nd/osnet osnet-internal >>>> >>>> so according to this change, is there any change to our >>>> dc_text_x86.xml? >>>> >>>> I build it with the changed path but got failed, is there other >>>> thing that i should change? >>>> >>>> the log is in the attachment. >>>> >>>> Thanks, >>>> Xun >>>>> Xun Ni: >>>>> >>>>> I was away and just got back. >>>>> >>>>> You can use DC to include driver/storage/scu in the >>>>> dc_text_sparc.xml and dc_text_x86.xml >>>>> >>>>> i.e: >>>>> >>>>> You need to add it to here: >>>>> >>>>> <software_data action="install"> >>>>> <name>pkg:/entire@latest</name> >>>>> <name>pkg:/group/system/solaris-large-server</name> >>>>> <name>pkg:/system/install/text-install</name> >>>>> <name>pkg:/driver/storage/lsc</name> >>>>> <name>pkg:/system/install/media/internal</name> >>>>> </software_data> >>>>> >>>>> >>>>> >>>>> >>>>> On 03/31/12 12:05 AM, xunni wrote: >>>>>> Hi, Mary: >>>>>> >>>>>> currently we have a new driver 'lsc' driver/storage/lsc, it >>>>>> doesn't exist in the 'server_install' group. but we want to test >>>>>> the installation. is there any way to use the TI to create the >>>>>> DVD to perform the test? >>>>>> >>>>>> Thanks, >>>>>> Xun >>>>>>> Xun Ni: >>>>>>> >>>>>>> If you look at http://ipkg.us.oracle.com and seach for >>>>>>> driver/storage/scu, it is in: >>>>>>> >>>>>>> auto_install >>>>>>> slim_install >>>>>>> server_install >>>>>>> redistributable >>>>>>> >>>>>>> So AI should work. >>>>>>> >>>>>>> http://ipkg.us.oracle.com/solaris11/dev/en/search.shtml?token=driver%2Fstorage%2Fscu+&action=Search >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 05/25/11 08:09 PM, xun.ni wrote: >>>>>>>> root@solaris:~# pkg info scu >>>>>>>> Name: driver/storage/scu >>>>>>>> Summary: Intel SCU SAS/SATA HBA driver >>>>>>>> Description: Intel Storage Controller Unit (SCU) SAS/SATA >>>>>>>> HBA Driver >>>>>>>> Category: Drivers/Storage >>>>>>>> State: Installed >>>>>>>> Publisher: on-nightly >>>>>>>> Version: 0.5.11 >>>>>>>> Build Release: 5.11 >>>>>>>> Branch: 0.166 >>>>>>>> Packaging Date: Wed May 25 06:13:57 2011 >>>>>>>> Size: 884.76 kB >>>>>>>> FMRI: >>>>>>>> pkg://on-nightly/driver/storage/[email protected],5.11-0.166:20110525T061357Z >>>>>>>> >>>>>>>> >>>>>>>> is this command? but i still can't find which group pkgs >>>>>>>> >>>>>>>> On 05/26/11 11:02, Mary Ding wrote: >>>>>>>>> Xun Ni: >>>>>>>>> >>>>>>>>> You can bring up the pkg repo and search to see where scu is in. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 05/25/11 07:58 PM, xun.ni wrote: >>>>>>>>>> is there a way to see which group packages my driver in? my >>>>>>>>>> driver name is scu >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Xun >>>>>>>>>> >>>>>>>>>> On 05/26/11 10:20, Mary Ding wrote: >>>>>>>>>>> Xun ni: >>>>>>>>>>> >>>>>>>>>>> I had included Karen on this and she is more famillar with >>>>>>>>>>> DC. If this is with TI, is your driver included in the >>>>>>>>>>> server_install group packages. If it does, then the install >>>>>>>>>>> should work. >>>>>>>>>>> >>>>>>>>>>> You can easily confirm this by booting the TI image and >>>>>>>>>>> check it out. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 05/25/11 07:13 PM, xun.ni wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hi, Marry: >>>>>>>>>>>> >>>>>>>>>>>> Thanks for your help, I need another confirm that if i >>>>>>>>>>>> have a new controller, and an old driver already in s11 >>>>>>>>>>>> but the driver don't support installation on the >>>>>>>>>>>> controller. After we modify the code , it supports the >>>>>>>>>>>> installation, >>>>>>>>>>>> And i use the DC to modify the publisher to my workspace, >>>>>>>>>>>> build an ISO, is this ISO support the installation. >>>>>>>>>>>> You know that if the driver support installation, the >>>>>>>>>>>> driver should be updated in both the repo and the >>>>>>>>>>>> ramdisk(miniroot), >>>>>>>>>>>> does the DC update both the repo and the ramdisk(miniroot)? >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Xun >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 05/19/11 02:25, Mary Ding wrote: >>>>>>>>>>>>> Xun Ni: >>>>>>>>>>>>> >>>>>>>>>>>>> You cannot use a dc xml to do AI install. >>>>>>>>>>>>> >>>>>>>>>>>>> If you want to test your binaries, I will suggest you do a >>>>>>>>>>>>> TI build. You make a copy of the dc_text_x86.xml, modify >>>>>>>>>>>>> the repo just like you did for the AI build. Remove the >>>>>>>>>>>>> entire and do the TI build. >>>>>>>>>>>>> >>>>>>>>>>>>> Then you can boot the iso or usb and test TI install and >>>>>>>>>>>>> it is easier to test your bits. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 05/18/11 04:30 AM, xun.ni wrote: >>>>>>>>>>>>>> Hi, Marry >>>>>>>>>>>>>> >>>>>>>>>>>>>> is it ok to remove the entire? I build the ISO >>>>>>>>>>>>>> successfully. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I create the DVD and boot from dvd, choose the custom >>>>>>>>>>>>>> boot menu, but it seems that the installation failed due >>>>>>>>>>>>>> to can't find manifest? >>>>>>>>>>>>>> >>>>>>>>>>>>>> should i choose the custom menu, other menu seems ok >>>>>>>>>>>>>> but i am not sure, the following is the log: >>>>>>>>>>>>>> >>>>>>>>>>>>>> =============================================== >>>>>>>>>>>>>> Hostname: solaris3, 2011, Oracle and/or its affiliates. >>>>>>>>>>>>>> All rights reserved. >>>>>>>>>>>>>> Remounting root read/write >>>>>>>>>>>>>> Probing for device nodes ... >>>>>>>>>>>>>> Preparing image for use >>>>>>>>>>>>>> Done mounting image >>>>>>>>>>>>>> Configuring devices. >>>>>>>>>>>>>> WARNING: No randomness provider enabled for /dev/random. >>>>>>>>>>>>>> Use cryptoadm(1M) to enable a provider. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Enter the URL for the AI manifest [HTTP, default]: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Obtaining manifest from the following location: >>>>>>>>>>>>>> /net/coloraxe.cn.oracle.com/builds/xunni/dc_ai_x86.xml >>>>>>>>>>>>>> /net/coloraxe.cn.oracle.com/builds/xunni/dc_ai_x86.xml: >>>>>>>>>>>>>> Scheme missing. >>>>>>>>>>>>>> >>>>>>>>>>>>>> solaris console login: >>>>>>>>>>>>>> Automated Installation started >>>>>>>>>>>>>> The progress of the Automated Installation can be >>>>>>>>>>>>>> followed by viewing >>>>>>>>>>>>>> the logfile at /tmp/install_log >>>>>>>>>>>>>> >>>>>>>>>>>>>> solaris console login: Invalid or incompatible manifest >>>>>>>>>>>>>> provided >>>>>>>>>>>>>> Please refer to the >>>>>>>>>>>>>> /var/svc/log/application-auto-installer:default.log file >>>>>>>>>>>>>> for details >>>>>>>>>>>>>> Mar 8 23:33:21 solaris svc.startd[8]: >>>>>>>>>>>>>> application/auto-installer:default failed fatally: >>>>>>>>>>>>>> transitioned to maintenance (see 'svcs -xv' for details) >>>>>>>>>>>>>> >>>>>>>>>>>>>> root@solaris:~# cat >>>>>>>>>>>>>> /var/svc/log/application-auto-installer:default.log >>>>>>>>>>>>>> [ Mar 8 23:33:15 Executing start method >>>>>>>>>>>>>> ("/lib/svc/method/auto-installer"). ] >>>>>>>>>>>>>> >>>>>>>>>>>>>> Automated Installation started >>>>>>>>>>>>>> The progress of the Automated Installation can be >>>>>>>>>>>>>> followed by viewing >>>>>>>>>>>>>> the logfile at /tmp/install_log >>>>>>>>>>>>>> >>>>>>>>>>>>>> Error instantiating manifest tree: >>>>>>>>>>>>>> Error creating in-memory copy of Manifest data. >>>>>>>>>>>>>> Error parsing xml file /tmp/ai.xml >>>>>>>>>>>>>> Invalid or incompatible manifest provided >>>>>>>>>>>>>> Please refer to the >>>>>>>>>>>>>> /var/svc/log/application-auto-installer:default.log file >>>>>>>>>>>>>> for details >>>>>>>>>>>>>> [ Mar 8 23:33:21 Method "start" exited with status 95. ] >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>> Xun >>>>>>>>>>>>>> On 05/18/11 11:27, Mary Ding wrote: >>>>>>>>>>>>>>> This will not work: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 1. You will need to add the on-extra nightly before solaris >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <publisher name="on-nightly"> >>>>>>>>>>>>>>> <origin name="file:///root/nightly/repo.redist"/> >>>>>>>>>>>>>>> </publisher> >>>>>>>>>>>>>>> <publisher name="solaris"> >>>>>>>>>>>>>>> <origin name="http://ipkg.us.oracle.com/solaris11/dev"/> >>>>>>>>>>>>>>> </publisher> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2. You will need to remove entire from the xml in order >>>>>>>>>>>>>>> for the build to work. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 05/17/11 08:24 PM, xun.ni wrote: >>>>>>>>>>>>>>>> Hi, Marry: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I set my repo before the 'solaris' publisher, see >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> <publisher name="on-nightly"> >>>>>>>>>>>>>>>> <origin name="file:///root/nightly/repo.redist"/> >>>>>>>>>>>>>>>> </publisher> >>>>>>>>>>>>>>>> <publisher name="solaris"> >>>>>>>>>>>>>>>> <origin name="http://ipkg.us.oracle.com/solaris11/dev"/> >>>>>>>>>>>>>>>> </publisher> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> but the log show failed: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 10:59:46 No matching version of entire can be >>>>>>>>>>>>>>>> installed: >>>>>>>>>>>>>>>> Reject: >>>>>>>>>>>>>>>> pkg://solaris/[email protected],5.11-0.151:20101027T142141Z >>>>>>>>>>>>>>>> Reason: All versions matching 'require' dependency >>>>>>>>>>>>>>>> pkg:/consolidation/osnet/osnet-incorporation are rejected >>>>>>>>>>>>>>>> Reject: >>>>>>>>>>>>>>>> pkg://on-nightly/consolidation/osnet/[email protected],5.11-0.166:20110517T104016Z >>>>>>>>>>>>>>>> Reason: Excluded by proposed incorporation 'entire' >>>>>>>>>>>>>>>> Reject: >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.151:20101026T180317Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.151.0.1:20101104T230646Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.152:20101112T165745Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.153:20101118T212652Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.154:20101203T190550Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.155:20101220T213006Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.156:20101230T214548Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.157:20110114T201511Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.158:20110127T191809Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.159:20110214T040231Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.160:20110226T064127Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.161:20110315T051502Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.162:20110325T170554Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.163:20110410T031009Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.164:20110422T153115Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pkg://solaris/consolidation/osnet/[email protected],5.11-0.165:20110510T013316Z >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 05/18/11 05:11, Mary Ding wrote: >>>>>>>>>>>>>>>>> Xun Ni: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> You did not do this correctly. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I will suggest you use the following repo instead of >>>>>>>>>>>>>>>>> using a custom script to replace the scu package: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> For your local repo where you had your package, you >>>>>>>>>>>>>>>>> need to list that first before the solaris repo: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> e.g: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> When I test my install nightly repo, this is what I did: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> <source> >>>>>>>>>>>>>>>>> <publisher name="install-nightly"> >>>>>>>>>>>>>>>>> <origin >>>>>>>>>>>>>>>>> name="file:/export/home/ding/sunstudio12u1patch/slim_source/packages/i386/nightly-nd/repo.redist"/> >>>>>>>>>>>>>>>>> </publisher> >>>>>>>>>>>>>>>>> <publisher name="solaris"> >>>>>>>>>>>>>>>>> <origin name="http://ipkg.us.oracle.com/solaris11/dev"/> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On 05/15/11 11:32 PM, xun.ni wrote: >>>>>>>>>>>>>>>>>> Hi, Dave: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I need to replace my package >>>>>>>>>>>>>>>>>> scu(driver/storage/scu) with the lastest using the >>>>>>>>>>>>>>>>>> DC, and currently my dc_ai_x86.xml and the custom >>>>>>>>>>>>>>>>>> script is in the attachment, The key error point is >>>>>>>>>>>>>>>>>> "Unable to install pkg://solaris/scu", my step is >>>>>>>>>>>>>>>>>> that i create a local IPS server with >>>>>>>>>>>>>>>>>> "/usr/lib/pkg.depotd -d /root/nightly/repo.redist/ -p >>>>>>>>>>>>>>>>>> 10000" and it contain the lastest package, and then i >>>>>>>>>>>>>>>>>> run "/usr/bin/distro_const build -v >>>>>>>>>>>>>>>>>> /root/dc_ai_x86.xml". I set a custom script to >>>>>>>>>>>>>>>>>> replace the package with my own but it failed, can >>>>>>>>>>>>>>>>>> you help me to figure out why it fail? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The output error is >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:29,012 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script INFO === >>>>>>>>>>>>>>>>>> Executing Custom Script Checkpoint === >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:29,012 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script INFO Custom >>>>>>>>>>>>>>>>>> Script provided is: '/export/home/scu_script.sh >>>>>>>>>>>>>>>>>> {PKG_IMAGE_PATH} scu' >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:29,012 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script INFO Custom >>>>>>>>>>>>>>>>>> Script to run is: '/export/home/scu_script.sh >>>>>>>>>>>>>>>>>> /export/home/dc/ai/build_data/pkg_image scu' >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:29,013 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script DEBUG >>>>>>>>>>>>>>>>>> Executing: /export/home/scu_script.sh >>>>>>>>>>>>>>>>>> /export/home/dc/ai/build_data/pkg_image scu >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:29,712 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script DEBUG >>>>>>>>>>>>>>>>>> /usr/bin/pkg -R >>>>>>>>>>>>>>>>>> /export/home/dc/ai/build_data/pkg_image uninstall scu >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:30,161 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script ERROR pkg: The >>>>>>>>>>>>>>>>>> image cannot be modified as it is currently in use by >>>>>>>>>>>>>>>>>> another package client: pkg on glasspaper.cn, pid 1257. >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:30,202 >>>>>>>>>>>>>>>>>> InstallationLogger.custom-script ERROR >>>>>>>>>>>>>>>>>> /export/home/scu_script.sh: Unable to install >>>>>>>>>>>>>>>>>> pkg://solaris/scu >>>>>>>>>>>>>>>>>> 2011-05-16 13:17:30,254 InstallationLogger >>>>>>>>>>>>>>>>>> ERROR Error occurred during execution of >>>>>>>>>>>>>>>>>> 'custom-script' checkpoint. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>> Xun >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> caiman-discuss mailing list >>>>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>> >> >> _______________________________________________ >> caiman-discuss mailing list >> [email protected] >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
