Sparse or full root Zones?

Hi,
having 'played' with zones for a while , the time has now come to start developing policies for their use within a consolidation programme. One area that is particularly unclear is; when do you use sparse zones as opposed to full root zones (disk space is not a problem within my organisation, so the decision can be technically rather than resource based).? To date I have not been able to find any documented recommendations and I would be interested in the views of the forum - thanks

IMHO, try to stick with sparse local zones unless the particular services to be provided by the zone require being able to write to any of the read-only file systems, especially /usr.
-mel

Similar Messages

  • Using a interface in a sparse-root zone on a different subnet

    Hello,
    is it possible to use interface ce0 for the global zone and configure interface ce1 for the non-global zone, but the interfaces are on a different subnet?
    ce0 ... 10.5.5.18 / global zone
    ce1 ... 192.168.5.18 / non-global zone
    using Solaris 5.10 Generic_125100-10
    I configured ce0 in the global zone (of course)
    and I plumbed ce1 also in the global zone - but configured ce1 in the zones definition
    zonecfg:oem> add net
    zonecfg:oem:net> set physical=ce1
    zonecfg:oem:net> set address=192.168.5.18The zone boots without any problems and it looks like this:
    [global zone]
    # ifconfig -a
    ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 10.5.5.18 netmask ffffff00 broadcast 10.5.5.255
            ether 0:3:ba:b0:53:39
    ce1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
            inet 0.0.0.0 netmask 0
            ether 0:3:ba:b0:53:39
    ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
            zone oem
            inet 192.168.5.18 netmask ffffff00 broadcast 192.168.5.255[non-global zone]
    # ifconfig -a
    ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
            inet 192.168.5.18 netmask ffffff00 broadcast 192.168.5.255I've read this is solved with GLDv3 drivers and exclusive IP instances mentioned in the blog http://blogs.sun.com/stw/entry/what_s_up_ce_doc -
    so the system shows
    # dladm show-link
    ce0             type: legacy    mtu: 1500       device: ce0
    ce1             type: legacy    mtu: 1500       device: ce1I get weird results even if I ping between the zones, I get "ICMP Destination unreachable"
    Can this be solved with a full-root zone ...?
    -- Nick

    here are my current settings:
    *[global zone]*
    # netstat -nr
    Routing Table: IPv4
      Destination           Gateway           Flags  Ref   Use   Interface
    10.5.5.0             10.5.5.18          U         1  10864 ce0      
    224.0.0.0            10.5.5.18          U         1      0 ce0      
    default             10.5.5 .1          UG        1  42839          
    127.0.0.1            127.0.0.1          UH        2 619817 lo0
    # ifconfig -a
    ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 10.5.5.18 netmask ffffff00 broadcast 10.5.5.255
            ether 0:3:ba:b0:53:39
    ce1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
            inet 0.0.0.0 netmask 0
            ether 0:3:ba:b0:53:39
    ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
            zone oem
            inet 192.168.5.18 netmask ffffff00 broadcast 192.168.5.255
    ! root@elba2:/ # route get 192.168.5.18
       route to: 192.168.5.18
    destination: 192.168.5.18
           mask: 255.255.255.255
      interface: ce1:1
          flags: <UP,DONE>
    recvpipe  sendpipe  ssthresh    rtt,ms rttvar,ms  hopcount      mtu     expire
           0         0         0         0         0         0      8232         0 *[sparse-root zone]*
    # netstat -nr
    Routing Table: IPv4
      Destination           Gateway           Flags  Ref   Use   Interface
    192.168.5.0          192.168.5.18         U         1     83 ce1:1    
    224.0.0.0            192.168.5.18         U         1      0 ce1:1    
    127.0.0.1            127.0.0.1            UH       19  86105 lo0:1    
    # ifconfig -a
    ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
            inet 192.168.5.18 netmask ffffff00 broadcast 192.168.1.255
    # route get 10.5.5.18
       route to: 10.5.5.18
    destination: 10.5.5.18
           mask: 255.255.255.255
      interface: ce0
          flags: <UP,DONE>
    recvpipe  sendpipe  ssthresh    rtt,ms rttvar,ms  hopcount      mtu     expire
           0         0         0         0         0         0      8232         0 Thank you for your time !
    -- Nick

  • Whole root or sparse root zones and patching

    Hi all,
    A while back, I did some cluster patching tests on a system with only sparse root zones, and one with whole root zones...and I seem to recall that the patch time was about equal which surprised me. I had thought the sparse root model mainly is patching the global zone, and even though patchadd may need to run through the sparse NGZ's...that it isn't doing much other than updating /var/sadm info in the NGZ's.
    Has anyone seen this to be true or if there are major patching improvements using a "sparse" root NGZ model over a "whole" root model?
    thanks much.

    My testing showed the same results and I was a bit surprised as well. As I dug into it further my understanding was that the majority of the patch application time goes into figuring out what to patch, not actually copying files around. That work must be done for the sparse zones in the same way as for the full root zones, we just save the few milliseconds of actually backing up and replacing the file.
    I suspect there is a large amount of slack that could be optimized in the patching process (both with and without zones), but I don't understand it nearly well enough to say that with any authority.

  • Patching JES  in whole root zone (where JES never installed in global zone)

    We ran into a problem today - we have a server (Solaris 10 x86 on 4150) with two full root zones. JES 5u1 was intsalled in each full root zone at a later date and never installed in the global zone. Now when trying to install the latest JES 5 patch cluster we have run into a problem. The patch cluster has a check that only lets it be run in the global zone. When we run it in the Global Zone - it exits every patch with a return code of 8 (software not installed).
    Is there any way we can run the patch bundle so it applies the patches to the no-global zones in this case? Will now installing teh shared components in the global zone then allow the patch cluster to run sucessfully.
    Thanks for any guidance here....

    Solution was to manually edit the patch cluster installation script and comment out the global zone check - it then installed perfecttly fine in the whole root zone

  • Sparse Root Zone using loopback refuses to shutdown

    New to zones, so been following along with the System Administration Guide: Solaris Containers-Resource Management and Solaris Zones doc from Sun (#817-1592). Everything seems ok with a plain jane zone, but I've run into trouble trying to use the loopback method to mount some other filesystems.
    The zone in question refuses to shut down no matter what method I use, and seemingly points to an RPC issue.
    using zlogin from the global zone, I get this, and it just hangs:
    # zlogin oracle_ods01 shutdown -i 0
    Shutdown started.    Fri Jul 24 08:40:02 PDT 2009
    Cannot send to root on /dev/pts/2
    open: No such device or address
    Cannot send to root on /dev/pts/2
    open: No such device or address
    showmount: oracle_ods01: RPC: Rpcbind failure - RPC: SuccessLogged into the zone:
    # shutdown -i 0
    Shutdown started.    Fri Jul 24 08:41:27 PDT 2009
    Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
    The system oracle_ods01 will be shut down in 1 minute
    Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
    The system oracle_ods01 will be shut down in 1 minute
    Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
    The system oracle_ods01 will be shut down in 1 minute
    showmount: oracle_ods01: RPC: Rpcbind failure - RPC: Success
    Changing to init state 0 - please waitBasically, I'm guessing its related to communication between the zones, but I'm not sure exactly what I'm missing. It's a default Solaris 10 install, so I've not disabled anything that wasn't already disabled. I did enable pools, but thats about it for the changes I've made so far. I guess I"m jus tnot sure if I should be looking at something I need to do in the global zone, or if I need to do something in the sparse root zone.
    Any insights appreciated, as I'm not sure that I didn't miss something along the way!
    Edited by: jef_e on Jul 24, 2009 8:52 AM
    I take that back - my other test zone also seems to be giving me issues. I initally issues a zone halt to shut it down, which seems to work for all zones. But is that recommended?

    New to zones, so been following along with the System Administration Guide: Solaris Containers-Resource Management and Solaris Zones doc from Sun (#817-1592). Everything seems ok with a plain jane zone, but I've run into trouble trying to use the loopback method to mount some other filesystems.
    The zone in question refuses to shut down no matter what method I use, and seemingly points to an RPC issue.
    using zlogin from the global zone, I get this, and it just hangs:
    # zlogin oracle_ods01 shutdown -i 0
    Shutdown started.    Fri Jul 24 08:40:02 PDT 2009
    Cannot send to root on /dev/pts/2
    open: No such device or address
    Cannot send to root on /dev/pts/2
    open: No such device or address
    showmount: oracle_ods01: RPC: Rpcbind failure - RPC: SuccessLogged into the zone:
    # shutdown -i 0
    Shutdown started.    Fri Jul 24 08:41:27 PDT 2009
    Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
    The system oracle_ods01 will be shut down in 1 minute
    Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
    The system oracle_ods01 will be shut down in 1 minute
    Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
    The system oracle_ods01 will be shut down in 1 minute
    showmount: oracle_ods01: RPC: Rpcbind failure - RPC: Success
    Changing to init state 0 - please waitBasically, I'm guessing its related to communication between the zones, but I'm not sure exactly what I'm missing. It's a default Solaris 10 install, so I've not disabled anything that wasn't already disabled. I did enable pools, but thats about it for the changes I've made so far. I guess I"m jus tnot sure if I should be looking at something I need to do in the global zone, or if I need to do something in the sparse root zone.
    Any insights appreciated, as I'm not sure that I didn't miss something along the way!
    Edited by: jef_e on Jul 24, 2009 8:52 AM
    I take that back - my other test zone also seems to be giving me issues. I initally issues a zone halt to shut it down, which seems to work for all zones. But is that recommended?

  • SAP Install on Solaris 10 Sparse Root Zone ../usr/sap

    Hi All,
    I was wondering if anyone is running SAP on Solaris 10, SAP EHP4 ECC 6.0 Oracle DB version 10. App and Db in a sparse root zone.
    When we initially created our SAP install the Directories containing <SID> and trans_<SID> was give to us as "/usr/sap"
    Since this is a sparse root zone, the /usr directory is read only. To accommodate SAP, a directory was created in the global zone for each of the containers ( we have ECC, PI, BW etc..) and then mounted as a filesystem in each container.   /usr/sap exists in every container, and it was supposed to be nothing more than a mount point for the <SID> and trans_<SID> NFS mounts. This /usr/sap directory exists on the global zone of our M5000 and the additional files and folders are eating up OS space.
    This creates me with two problems.
    1. WHen I take a snapshot, I can't recover the zone in a automatic fashion because the local zone can not see the global /usr directory, so I have to recover that folder/file manually.
    2. I don't know exactly, but files are being created in the usr/sap directory that is causing internal drives to grow quickly.
    To resolve our issues it was determined that the best course of action is to remove the connection to the global zone by creating a /sap directory in each container and linking it as /usr/sap.  The /sap directory will be an NFS/FC mount point and that will fix the issue of disk space usage and backup recovery.
    Does anyone have another way to solve this problem or any suggestions that we should do something different. ?

    I use sparse zones on Solaris with ZFS.
    I delegate filesystems to the zone.
    root@global ~# zonecfg -z zone_name info
    zonename: zone_name
    zonepath: /zfs_zones/zone_name
    brand: native
    autoboot: true
    bootargs:
    pool:
    limitpriv:
    scheduling-class:
    ip-type: shared
    hostid:
    inherit-pkg-dir:
            dir: /lib
    inherit-pkg-dir:
            dir: /platform
    inherit-pkg-dir:
            dir: /sbin
    inherit-pkg-dir:
            dir: /usr
    net:
            address: w.x.y.z/nn
            physical: nxge0
            defrouter: w.x.y.z
    dataset:
            name: zfs_zones/zone_name/oracle
    dataset:
            name: zfs_zones/zone_name/sapmnt
    dataset:
            name: zfs_zones/zone_name/usr_sap
    root@zone_name ~# zfs list -o name,mountpoint
    NAME                                     MOUNTPOINT
    zfs_zones/zone_name/oracle               /oracle
    zfs_zones/zone_name/oracle/SID_mirrlogA  /oracle/SID/mirrlogA
    zfs_zones/zone_name/oracle/SID_mirrlogB  /oracle/SID/mirrlogB
    zfs_zones/zone_name/oracle/SID_oraarch   /oracle/SID/oraarch
    zfs_zones/zone_name/oracle/SID_origlogA  /oracle/SID/origlogA
    zfs_zones/zone_name/oracle/SID_origlogB  /oracle/SID/origlogB
    zfs_zones/zone_name/oracle/SID_sapdata1  /oracle/SID/sapdata1
    zfs_zones/zone_name/oracle/SID_sapdata2  /oracle/SID/sapdata2
    zfs_zones/zone_name/oracle/SID_sapdata3  /oracle/SID/sapdata3
    zfs_zones/zone_name/oracle/SID_sapdata4  /oracle/SID/sapdata4
    zfs_zones/zone_name/sapmnt               /sapmnt
    zfs_zones/zone_name/usr_sap              /usr/sap
    Edited by: RUSS HANSEN on Dec 14, 2011 8:52 PM

  • SMC - Solaris Management Console in whole root zone

    Hi,
    Is it possible to run smc in whole root zone? Is there a howto for this?
    I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
    I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.
    Thanks...

    Hi dnzrnd,
    dnzrnd wrote:
    Is it possible to run smc in whole root zone? Is there a howto for this?
    I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
    I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.SunMC should install and run fine in a whole-root zone: I haven't heard of any problems. Are you maybe confusing "Sun Management Center" (this forum) with "Solaris Management Console" (a different product)?
    Regards,
    [email protected]
    http://www.HalcyonInc.com
    New !! : http://forums.HalcyonInc.com !!

  • Solaris Management Console in whole root zones

    Is it possible to run smc in whole root zone? Is there a howto for this? I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
    I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.

    Hi dnzrnd,
    dnzrnd wrote:
    Is it possible to run smc in whole root zone? Is there a howto for this?
    I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
    I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.SunMC should install and run fine in a whole-root zone: I haven't heard of any problems. Are you maybe confusing "Sun Management Center" (this forum) with "Solaris Management Console" (a different product)?
    Regards,
    [email protected]
    http://www.HalcyonInc.com
    New !! : http://forums.HalcyonInc.com !!

  • Whole root zone doesn't run Solaris Management Console

    All
    I created a couple of Whole Root zone's, but the SMC is not working. It can't even be found. (However, on the "sparse" zones, it works fine.)
    I ran:
    pkginfo SUNWsmcmd
    and got:
    system SUNWsmcmd System Management Agent applications and utilities
    So, it seems like it's installed, but it ain't working on any of the whole-root zones.
    Anyone have any ideas on this one?
    Thank you
    SB

    I think I have the same problem -
    One global zone and one whole-root zone installed.
    I access the server withhttps://servername:6789/containersthen I can see Solaris Container Manager 3.6.1but when I select it, I get
    There was an error while connecting to the Solaris Container Manager service. Restart the services and login again.
    Restart Sun Management Center services and log in again.I restarted meanwhile every service, but I did not a server reboot.
    # zoneadm list -vc
      ID NAME             STATUS         PATH                         
       0 global           running        /                            
       1 mantis-ldap      running        /var/zone/mantis-ldapWhat logfile could help to clarify that?
    SMC release is 3.6.1
    -- Nick

  • Sparse or whole root - what is really default

    There is a note in zones documentation that sparse-root model is the default one. But after creating zone (using 'create', not 'create -b' ! ):
    zonecfg -z z1
    zonecfg:z1> create
    zonecfg:z1> set zonepath=/zones/z1
    zonecfg:z1> set autoboot=true
    zonecfg:z1> ...
    zonecfg:z1> export -f /root/zones/z1.cfg
    zonecfg:z1> exit
    I can see in the file that:
    # cat /root/zones/z1.cfg
    create -b
    set zonepath=/zones/z1
    Why there is 'create -b' in the exported file ?!?!
    przemol

    Simple; see the manualpage for zonecfg(1M). If you
    use create a zone the system automaticly presents you
    with some inherit-pkg-dir entries. When you export
    your configuration it sets these up as well, but in
    order to make sure they aren't defined twice it
    starts with a clear configuration.Thanks for the answer. Indeed, it is obvious now :-)
    przemol

  • SMC doesn't work in any solaris 10 whole-root zones

    All
    Are you aware of SUN not designing whole-root zones to work with Solaris Management Console?
    None of my solaris 10 whole-root zones/containers will run Solaris Management Console. Very, very frustrating!
    Anyone have a trick to get around this crazy design??
    Thank you!
    SB

    Thanks for your help!
    Yes, i see all font types.
    But maybe i havn't explained my problem good enough:
    I have a FLA-File which works great in Flash CS3: everything – even on different computers – is okay!
    The same FLA-File on the same computer in Flash CS6: the font-rendering is broken!
    In CS6 there seems to be a difference between textfields made via ActionScript and textfields on the stage: see the attached file in my first post.

  • Unable to create a whole root zone

    Hi Folks,
    I wanted to create a whole-root zone. I am unable to create one :(. Did some one encounter this problem ?.
    BTW: I have SC 3.2 installed on this two node cluster. I was able to validate our Data services on this setup without any problem Now I am trying to experiment with zones, by creating zones. I am unable to move further with my validation of our data services on zones.
    *) mkdir -m 700 /export/zone-1
    *) The version of the OS used
    # cat /etc/release
    Solaris 10 11/06 s10s_u3wos_09 SPARC
    Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 01 November 2006
    # zonecfg -z zone-1
    zone-1: No such zone configured
    Use 'create' to begin configuring a new zone.
    zonecfg:zone-1> create
    zonecfg:zone-1> remove inherit-pkg-dir dir=/sbin
    zonecfg:zone-1> remove inherit-pkg-dir dir=/usr
    zonecfg:zone-1> remove inherit-pkg-dir dir=/platform
    zonecfg:zone-1> remove inherit-pkg-dir dir=/lib
    zonecfg:zone-1> set autoboot=true
    zonecfg:zone-1> set zonepath=/export/zone-1
    zonecfg:zone-1> add net
    zonecfg:zone-1:net> set address=192.18.75.237
    zonecfg:zone-1:net> set physical=eri0
    zonecfg:zone-1:net> end
    zonecfg:zone-1> info
    zonename: zone-1
    zonepath: /export/zone-1
    autoboot: true
    pool:
    limitpriv:
    net:
    address: 192.18.75.237
    physical: eri0
    zonecfg:zone-1> verify
    zonecfg:zone-1> commit
    zonecfg:zone-1> exit
    # cat /etc/zones/zone-1.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
    <!--
    DO NOT EDIT THIS FILE. Use zonecfg(1M) instead.
    -->
    <zone name="zone-1" zonepath="/export/zone-1" autoboot="true">
    <network address="192.18.75.237" physical="eri0"/>
    </zone>
    # zoneadm list -civ
    ID NAME STATUS PATH
    0 global running /
    - zone-1 configured /export/zone-1
    # zoneadm -z zone-1 verify
    # zoneadm -z zone-1 install
    Preparing to install zone <zone-1>.
    Creating list of files to copy from the global zone.
    Copying <6080> files to the zone.
    Initializing zone product registry.
    Determining zone package initialization order.
    Preparing to initialize <1071> packages on the zone.
    Initialized <1071> packages on zone.
    Zone <zone-1> is initialized.
    Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
    Installation of <1> packages was skipped.
    Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
    The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
    # pkginfo -i SUNWsczr
    application SUNWsczr Sun Cluster (non-global zones support)
    # pkginfo -i SUNWsczr
    application SUNWsczr Sun Cluster (non-global zones support)
    # pkginfo -i SUNWdtlog
    system SUNWdtlog System boot for Desktop Login
    # pkginfo -i SUNWsmmgr
    system SUNWsmmgr System Management Agent Startup scripts
    *** package <SUNWsczr> failed to install with fatal errors:
    WARNING: attribute verification of </export/zone-1/root/etc/init.d/stoprgm> failed
    pathname does not exist
    NOTE: When the package <SUNWsczr> was installed in the global zone, the file <etc/init.d/stoprgm> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone <zone-1> in the file </export/zone-1/root/etc/init.d/stoprgm>.
    ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWsczr/save/pspool/SUNWsczr/archive.
    pkgadd: ERROR: class action script did not complete successfully
    Installation of <SUNWsczr> on zone <zone-1> failed.
    *** package <SUNWnisr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nis> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <etc/nsswitch.nis> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/nsswitch.nis>.
    WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nisplus> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <etc/nsswitch.nisplus> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/nsswitch.nisplus>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nisplus> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <lib/svc/method/nisplus> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/nisplus>.
    WARNING: attribute verification of </export/zone-1/root/var/nis/NIS+LDAPmapping.template> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <var/nis/NIS+LDAPmapping.template> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/nis/NIS+LDAPmapping.template>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ nis/client.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/nisplus.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/rex.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/nisplus.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rex.xml> failed
    pathname does not exist
    Installation of <SUNWnisr> on zone <zone-1> partially
    failed.
    *** package <SUNWypr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/var/yp/updaters> failed
    pathname does not exist
    NOTE: When the package <SUNWypr> was installed in the global zone,
    the file <var/yp/updaters> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/yp/updaters>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/passwd.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/server.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/update.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/xfr.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/passwd.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/server.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/update.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/xfr.xml> failed
    pathname does not exist
    Installation of <SUNWypr> on zone <zone-1> partially
    failed.
    *** package <SUNWipplr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWipplr/save/pspool/SUNWipplr/reloc/var/svc/manifest/applic ation/print/ipp-listener.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/ipp-listener.xml> failed
    pathname does not exist
    Installation of <SUNWipplr> on zone <zone-1> partially
    failed.
    *** package <SUNWaccr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-sar> failed
    pathname does not exist
    NOTE: When the package <SUNWaccr> was installed in the global zone,
    the file <lib/svc/method/svc-sar> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/svc-sar>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWaccr/save/pspool/SUNWaccr/reloc/var/svc/manifest/system/s ar.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/sar.xml> failed
    pathname does not exist
    Installation of <SUNWaccr> on zone <zone-1> partially
    failed.
    *** package <SUNWbsr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/rpld.conf> failed
    pathname does not exist
    NOTE: When the package <SUNWbsr> was installed in the global zone,
    the file <etc/rpld.conf> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/rpld.conf>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/ra rp.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/rp c/bootparams.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rarp.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/bootparams.xml> failed
    pathname does not exist
    Installation of <SUNWbsr> on zone <zone-1> partially
    failed.
    *** package <SUNWdhcsr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/init.d/dhcp> failed
    pathname does not exist
    NOTE: When the package <SUNWdhcsr> was installed in the global zone,
    the file <etc/init.d/dhcp> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/init.d/dhcp>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWdhcsr/save/pspool/SUNWdhcsr/reloc/var/svc/manifest/networ k/dhcp-server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dhcp-server.xml> failed
    pathname does not exist
    Installation of <SUNWdhcsr> on zone <zone-1> partially
    failed.
    *** package <SUNWatfsr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-autofs> failed
    pathname does not exist
    NOTE: When the package <SUNWatfsr> was installed in the global zone,
    the file <lib/svc/method/svc-autofs> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/svc-autofs>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWatfsr/save/pspool/SUNWatfsr/reloc/var/svc/manifest/system /filesystem/autofs.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/filesystem/autofs.xml> failed
    pathname does not exist
    Installation of <SUNWatfsr> on zone <zone-1> partially
    failed.
    *** package <SUNWkdcr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWkdcr/save/pspool/SUNWkdcr/reloc/var/svc/manifest/network/ security/krb5_prop.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/security/krb5_prop.xml> failed
    pathname does not exist
    Installation of <SUNWkdcr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.gif> failed
    pathname does not exist
    NOTE: When the package <SUNWapch2r> was installed in the global zone,
    the file <var/apache2/icons/world2.gif> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.gif>.
    WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.png> failed
    pathname does not exist
    NOTE: When the package <SUNWapch2r> was installed in the global zone,
    the file <var/apache2/icons/world2.png> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.png>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWapch2r/save/pspool/SUNWapch2r/reloc/var/svc/manifest/netw ork/http-apache2.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/http-apache2.xml> failed
    pathname does not exist
    Installation of <SUNWapch2r> on zone <zone-1> partially
    failed.
    *** package <SUNWbindr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbindr/save/pspool/SUNWbindr/reloc/var/svc/manifest/networ k/dns/server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dns/server.xml> failed
    pathname does not exist
    Installation of <SUNWbindr> on zone <zone-1> partially
    failed.
    *** package <SUNWbnur> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbnur/save/pspool/SUNWbnur/reloc/var/svc/manifest/network/ uucp.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/uucp.xml> failed
    pathname does not exist
    Installation of <SUNWbnur> on zone <zone-1> partially
    failed.
    *** package <SUNWcnsr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ chargen.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ daytime.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ discard.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ echo.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ time.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/chargen.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/daytime.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/discard.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/echo.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/time.xml> failed
    pathname does not exist
    Installation of <SUNWcnsr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/etc/lp/fd/pr.fd> failed
    pathname does not exist
    NOTE: When the package <SUNWpsr> was installed in the global zone,
    the file <etc/lp/fd/pr.fd> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/lp/fd/pr.fd>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/print-svc> failed
    pathname does not exist
    NOTE: When the package <SUNWpsr> was installed in the global zone,
    the file <lib/svc/method/print-svc> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/print-svc>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWpsr/save/pspool/SUNWpsr/reloc/var/svc/manifest/applicatio n/print/server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/server.xml> failed
    pathname does not exist
    Installation of <SUNWpsr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/var/snmp/mib/sun.mib> failed
    pathname does not exist
    NOTE: When the package <SUNWsacom> was installed in the global zone,
    the file <var/snmp/mib/sun.mib> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/snmp/mib/sun.mib>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.dmi> is corrupt
    file size <373> expected <1125> actual
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.snmpdx& gt; is corrupt
    file size <382> expected <685> actual
    ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.dmi> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.snmpdx> failed
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/dmi.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/snmpdx.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/dmi.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/snmpdx.xml> failed
    pathname does not exist
    Installation of <SUNWsacom> on zone <zone-1> partially
    failed.
    *** package <SUNWdtlog> failed to install with fatal errors:
    WARNING: attribute verification of </export/zone-1/root/etc/init.d/dtlogin> failed
    pathname does not exist
    NOTE: When the package <SUNWdtlog> was installed in the global zone,
    the file <etc/init.d/dtlogin> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/init.d/dtlogin>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-dtlogin> failed
    pathname does not exist
    NOTE: When the package <SUNWdtlog> was installed in the global zone,
    the file <lib/svc/method/svc-dtlogin> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/svc-dtlogin>.
    ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/archive.
    pkgadd: ERROR: class action script did not complete successfully
    Installation of <SUNWdtlog> on zone <zone-1> failed.
    *** package <SUNWnfssr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nfs-server> failed
    pathname does not exist
    NOTE: When the package <SUNWnfssr> was installed in the global zone,
    the file <lib/svc/method/nfs-server> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/nfs-server>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/rquota.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/rquota.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/server.xml> failed
    pathname does not exist
    Installation of <SUNWnfssr> on zone <zone-1> partially
    failed.
    *** package <SUNWntpr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/inet/ntp.server> failed
    pathname does not exist
    NOTE: When the package <SUNWntpr> was installed in the global zone,
    the file <etc/inet/ntp.server> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/inet/ntp.server>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/xntp> failed
    pathname does not exist
    NOTE: When the package <SUNWntpr> was installed in the global zone,
    the file <lib/svc/method/xntp> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/xntp>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWntpr/save/pspool/SUNWntpr/reloc/var/svc/manifest/network/ ntp.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ntp.xml> failed
    pathname does not exist
    Installation of <SUNWntpr> on zone <zone-1> partially
    failed.
    *** package <SUNWftpr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWftpr/save/pspool/SUNWftpr/reloc/var/svc/manifest/network/ ftp.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ftp.xml> failed
    pathname does not exist
    Installation of <SUNWftpr> on zone <zone-1> partially
    failed.
    *** package <SUNWrcapr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcapr/save/pspool/SUNWrcapr/reloc/var/svc/manifest/system /rcap.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/rcap.xml> failed
    pathname does not exist
    Installation of <SUNWrcapr> on zone <zone-1> partially
    failed.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcmdr/save/pspool/SUNWrcmdr/reloc/var/svc/manifest/networ k/talk.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/comsat.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/finger.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/login.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rexec.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rstat.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rusers.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/spray.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/wall.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/shell.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/talk.xml> failed
    pathname does not exist
    Installation of <SUNWrcmdr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> ; failed
    pathname does not exist
    NOTE: When the package <SUNWsmmgr> was installed in the global zone,
    the file <etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> was also installed. Af

    Hello,
    I still get the errors.
    # zonecfg -z zone-one
    zone-one: No such zone configured
    Use 'create' to begin configuring a new zone.
    zonecfg:zone-one> create -b
    zonecfg:zone-one> set autoboot=true
    zonecfg:zone-one> set zonepath=/export/zone-one
    zonecfg:zone-one> add net
    zonecfg:zone-one:net> set physical=eri0
    zonecfg:zone-one:net> set address=192.18.xx.xxx
    zonecfg:zone-one:net> end
    zonecfg:zone-one> verify
    zonecfg:zone-one> commit
    zonecfg:zone-one> exit
    # zoneadm -z zone-one verify
    # zoneadm -z zone-one install
    Preparing to install zone <zone-one>.
    Creating list of files to copy from the global zone.
    Copying <6080> files to the zone.
    Initializing zone product registry.
    Determining zone package initialization order.
    Preparing to initialize <1071> packages on the zone.
    Initialized <1071> packages on zone.
    Zone <zone-one> is initialized.
    Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
    Installation of <1> packages was skipped.
    Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
    The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
    _DD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Replication whole root zones

    Hello,
    I need to configure whole root zones which needs to be replicated to a secondary site.
    Would like to know if there is a way by which i can avoid replicating the swap file in a whole root zone configuration.
    Please advice.
    Thanks & Regards
    Ranjit

    I don't understand your question. What swap file are you referring to? There's nothing about a whole-root zone that requires a swap file be present.
    Darren

  • Secure shell in a whole root zone

    Hello,
    I have two whole root zones running on my Solaris 10 server along with the global zone. I am able to secure shell in to the global zone, but not the whole root zones. Secure shell does not appear to be running in the whole root zones. I've tried svcadm restart ssh in the whole root zones,but no luck. What do I need to do to get secure shell working on the whole root zones?

    to create the necessary keys -
    # ssh-keygen -b 1024 -t rsa1 -f /etc/ssh/ssh_host_key -N ""
    # ssh-keygen -b 1024 -t rsa -f /etc/ssh/ssh_host_rsa_key -N ""
    # ssh-keygen -b 1024 -t dsa -f /etc/ssh/ssh_host_dsa_key -N ""-- Nick

  • Whole root zone and packages

    I installed in my global zone the "Entire Distribution" of Solaris 10 and some software from Companion CD.
    Now I would like install a "whole root zone" with a basic set of packages (like "End User Distribution") and without the packages
    from the Companion CD.
    I can use pkgrm to delete the unnecessary packages in my whole root zone.
    But is there a more elegant way to get a whole root zone only with basic packages?
    Regards. P.

    The "easy" way would be to do a minimal installation in the Global zone and then install the required services in the local zone.
    HTH,
    Roger S.

Maybe you are looking for

  • Windows cant download update, error code 80071A30 comes up

    Hi , for some reason my updates wont install, an erroe code 80071A30 keeps coming up. Any ideas whats going on?

  • Workspace template selection

    Hi gents, In my beekpr, within my enterprise i have a list of workspaces listed in the workspace templates. (basic team, Project, Beeki, community of practice etc.) When i create a workspace using outlook, i cannot select which type of workspace i wa

  • Color printing kaput

    I sure hope someone can help me. A couple of months ago my color printing started looking terrible.......dull and grainy.  It only got worse from there.  Anything printed from iphoto turned out garish high-contrast red/yellow/black, while Preview con

  • Issue with general settings

    Hi Has anyone had an issue with general settings where by you go into settings and then select 'general' and the phone dumps you back to the main screen. This happens every time and I now can not chnage a large number of settings. I have just updated

  • Browse sequence - webhelp

    I need one confirmation: I've generated a help file using RH6 and browse sequence editor works fine in HTML Help. Will it not work in WebHelp??? What should i do to make this work in Webhelp too??