Re: [zones-discuss] solaris 10 branded zone
> > I used the following > cd / > find . \( \( -fstype nfs -o -fstype autofs \) -prune \) -o -print| egrep > -v "^./proc|^./system|^./devices|^./dev|^./export/home|^./home|^./tmp" > |cpio -oc > /export/home/oryx.cpio > > But that is only if you have zfs root and separate /var. > Another solution, which is a lot simpler would be to use the -y parameter to flar: flar create -c -L pax -n name -y /var /path/to/flar Note, that i also used compression (-c) -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
instead of using a vnic - i shared real hardware: e1000g0 - and that seemed to clear up the problem. i can ping up and down. i still may have made a typo or something with the crossbow vnic setup or something else that i inadvertently corrected when i switched to an actual hardware device or there may be a bug, i don't know - but it is cleared up now. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
now i am having routing problems - on the global zone if i do an ifconfig: init...@dogpatch:~$ ifconfig -a lo0: flags=2001000849 mtu 8232 index 1 inet 127.0.0.1 netmask ff00 lo0:1: flags=2001000849 mtu 8232 index 1 zone csuite inet 127.0.0.1 netmask ff00 e1000g0: flags=1100843 mtu 1500 index 2 inet 192.168.11.3 netmask ff00 broadcast 192.168.11.255 vboxnet0: flags=201100843 mtu 1500 index 3 inet 192.168.56.1 netmask ff00 broadcast 192.168.56.255 vnic0_0: flags=1100843 mtu 9000 index 4 inet 192.168.30.254 netmask ff00 broadcast 192.168.30.255 vnic0_3: flags=1100843 mtu 9000 index 5 inet 192.168.30.5 netmask ff00 broadcast 192.168.30.255 vnic0_3:1: flags=1100843 mtu 9000 index 5 zone csuite inet 192.168.30.4 netmask ff00 broadcast 192.168.30.255 lo0: flags=2002000849 mtu 8252 index 1 inet6 ::1/128 lo0:1: flags=2002000849 mtu 8252 index 1 zone csuite inet6 ::1/128 and i can see the shared vnic: vnic0_3 with 2 different ip addresses. if i do a zlogin to the local zone and do an ifconfig: bash-3.00# ifconfig -a lo0:1: flags=2001000849 mtu 8232 index 1 inet 127.0.0.1 netmask ff00 vnic0_3:1: flags=1100843 mtu 9000 index 5 inet 192.168.30.4 netmask ff00 broadcast 192.168.30.255 lo0:1: flags=2002000849 mtu 8252 index 1 inet6 ::1/128 bash-3.00# netstat -r Routing Table: IPv4 Destination Gateway Flags Ref Use Interface - - -- - 192.168.30.0 192.168.30.4 U 1 9 vnic0_3:1 i see the same ip address and that the ip address is the gateway. however, if i pring the ip address in the global zone: bash-3.00# ping 192.168.30.4 192.168.30.4 is alive bash-3.00# ping 192.168.30.5 no answer from 192.168.30.5 it doesn't answer - why would i have trouble pinging the global zone from the local zone? i usually have the same problem the other way - the gloabl zone can't ping the local zone. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
ok, my mistake - i had used the same ip address for both the local and global zone when i had a shared vnic. i had assumed they could be the same since the loopback (127.0.0.1) was the same for both, and it appeared to be shared, as well. using 2 different ip addresses cleared up the problem and the solaris 10 branded zone booted without complaint. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
Unfortunately, exclusive-stack solaris10-branded zones aren't supported yet. The zone will fail to configure and boot if you make it exclusive-stack. Jordan On 01/11/10 06:22 PM, HeCSa wrote: Hi! On Mon, 2010-01-11 at 16:21 -0800, xx wrote: i am having trouble getting rid of the warning: WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. when i boot the zone - i get: init...@dogpatch:~$ pfexec zoneadm -z csuite boot WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. Have you configured the ip-type as exclusive for that zone? Best regards, HeCSa. i know that it is present in the global zone: init...@dogpatch:~$ dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID vnic0_0 etherstub0 0 2:8:20:9c:9d:1f random 0 vnic0_1 etherstub0 0 2:8:20:bc:91:d5 random 0 vnic0_2 etherstub0 0 2:8:20:a1:e3:5e random 0 vnic0_3 etherstub0 0 2:8:20:a4:32:81 random 0 it is not plumbed- so i tried to plumb it - i added /etc/hostname.vnic0_3, put an ip address in it, and rebooted - but then the zone boot complained that the vnic was in use by the global zone. my zone id configured: init...@dogpatch:~$ zonecfg -z csuite info zonename: csuite zonepath: /zones/csuite brand: solaris10 autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: shared hostid: net: address: 192.168.30.4 physical: vnic0_3 defrouter not specified ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
Hi! On Mon, 2010-01-11 at 16:21 -0800, xx wrote: > i am having trouble getting rid of the warning: > WARNING: skipping network interface 'vnic0_3' which may not be > present/plumbed in the global zone. > > when i boot the zone - i get: > init...@dogpatch:~$ pfexec zoneadm -z csuite boot > WARNING: skipping network interface 'vnic0_3' which may not be > present/plumbed in the global zone. Have you configured the ip-type as exclusive for that zone? Best regards, HeCSa. > > i know that it is present in the global zone: > init...@dogpatch:~$ dladm show-vnic > LINK OVER SPEED MACADDRESSMACADDRTYPE VID > vnic0_0 etherstub0 0 2:8:20:9c:9d:1f random 0 > vnic0_1 etherstub0 0 2:8:20:bc:91:d5 random 0 > vnic0_2 etherstub0 0 2:8:20:a1:e3:5e random 0 > vnic0_3 etherstub0 0 2:8:20:a4:32:81 random 0 > > it is not plumbed- so i tried to plumb it - i added /etc/hostname.vnic0_3, > put an ip address in it, and rebooted - but then the zone boot complained > that the vnic was in use by the global zone. > > my zone id configured: > init...@dogpatch:~$ zonecfg -z csuite info > zonename: csuite > zonepath: /zones/csuite > brand: solaris10 > autoboot: false > bootargs: > pool: > limitpriv: > scheduling-class: > ip-type: shared > hostid: > net: > address: 192.168.30.4 > physical: vnic0_3 > defrouter not specified ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
i am having trouble getting rid of the warning: WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. when i boot the zone - i get: init...@dogpatch:~$ pfexec zoneadm -z csuite boot WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. i know that it is present in the global zone: init...@dogpatch:~$ dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID vnic0_0 etherstub0 0 2:8:20:9c:9d:1f random 0 vnic0_1 etherstub0 0 2:8:20:bc:91:d5 random 0 vnic0_2 etherstub0 0 2:8:20:a1:e3:5e random 0 vnic0_3 etherstub0 0 2:8:20:a4:32:81 random 0 it is not plumbed- so i tried to plumb it - i added /etc/hostname.vnic0_3, put an ip address in it, and rebooted - but then the zone boot complained that the vnic was in use by the global zone. my zone id configured: init...@dogpatch:~$ zonecfg -z csuite info zonename: csuite zonepath: /zones/csuite brand: solaris10 autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: shared hostid: net: address: 192.168.30.4 physical: vnic0_3 defrouter not specified -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
ok - that appears to work: init...@dogpatch:/virtualbox# zoneadm -z csuite install -a /virtualbox/s10.cpio -u WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. Log File: /var/tmp/csuite.install_log.XEaWcB Installing: This may take several minutes... Postprocessing: This may take a while... Postprocess: Updating the image to run within a zone Result: Installation completed successfully. Log File: /zones/csuite/root/var/log/csuite.install13777.log and it booted: bash-3.00# uname -a SunOS csuite 5.10 Generic_Virtual i86pc i386 i86pc and it gave me a 64 bit machine - even though i'm missing some fancy hardware: # isainfo -v 64-bit amd64 applications sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx cmov amd_sysc cx8 tsc fpu 0x2 32-bit i386 applications sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx cmov amd_sysc cx8 tsc fpu 0x2 thanks so much everybody for helping me! david -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
xx wrote: init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio -u WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. Log File: /var/tmp/csuite.install_log.79aGOA Error: Unknown archive format. Must be a flash archive, a cpio archive (can also be gzipped or bzipped), a pax XUSTAR archive, or a level 0 ufsdump archive. ERROR: Installation aborted. do i need to label it as a cpio archive somehow? I think you've hit a bug in the code. Can you re-run the command with an absolute path to the flar. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
ok - i re-created the s10.flar: # flar create -L cpio -n myflash /export/home/s10.cpio Archive format requested is cpio This archiver format is NOT VALID for flash installation of ZFS root pool. This format is useful for installing the system image into a zone. Reissue command without -L option to produce an archive for root pool install. Full Flash Checking integrity... Integrity OK. Running precreation scripts... Precreation scripts done. Determining the size of the archive... The archive will be approximately 3.21GB. 6746651 blocks Creating the archive... 6746653 blocks Archive creation complete. Running postcreation scripts... Postcreation scripts done. Running pre-exit scripts... Pre-exit scripts done. i copied it to the global zone: init...@dogpatch:/virtualbox# scp r...@192.168.11.4:/export/home/s10.cpio . Password: s10.cpio 100% |*| 3294 MB07:30 init...@dogpatch:/virtualbox# ls -l total 20440460 -rw-r--r-- 1 65535other151 Oct 2 02:28 autoresponse -rw-r--r-- 1 65535other 2314 Oct 2 02:28 ReadMe.txt -rw-r--r-- 1 root root 3454295946 Dec 9 09:10 s10.cpio -rw-r--r-- 1 root root 4039699747 Dec 8 16:09 s10.flar -rw-r--r-- 1 initial staff2563440640 Oct 17 13:35 sol-10-u8-ga-x86-dvd.iso -rw-r--r-- 1 initial staff4208274 Oct 17 11:19 UserManual.pdf -rw-r--r-- 1 initial staff197888000 Oct 17 11:19 VirtualBox-3.0.8-53138-SunOS.tar -rw-r--r-- 1 65535other197806592 Oct 2 02:28 VirtualBox-3.0.8-SunOS-r53138.pkg -rw-r--r-- 1 65535other 67072 Oct 2 02:28 VirtualBoxKern-3.0.8-SunOS-r53138.pkg init...@dogpatch:/virtualbox# rm s10.flar then i tried to install it: init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. ERROR: you must specify -u (sys-unconfig) or -p (preserve identity). solaris10 brand usage: install -u | -p [-v | -s] -a archive | -d directory. The -a archive option specifies an archive name which can be a flar, tar, pax or cpio archive. The -d directory option specifies an existing directory. The -u option unconfigures the zone, -p preserves the configuration. usage: install [-x nodataset] [brand-specific args] Install the configuration on to the system. The -x nodataset option can be used to prevent the creation of a new ZFS file system for the zone (assuming the zonepath is within a ZFS file system). All other arguments are passed to the brand installation function; see brands(5) for more information. init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio -u zoneadm: zone 'csuite': zone is incomplete; uninstall required. init...@dogpatch:/virtualbox# zoneadm -z csuite uninstall Are you sure you want to uninstall zone csuite (y/[n])? y init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio -u WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. Log File: /var/tmp/csuite.install_log.79aGOA Error: Unknown archive format. Must be a flash archive, a cpio archive (can also be gzipped or bzipped), a pax XUSTAR archive, or a level 0 ufsdump archive. ERROR: Installation aborted. do i need to label it as a cpio archive somehow? -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
xx wrote: according to my notes, i create the flar with: #flar create -n myflash /export/home/s10-.flar i picked up the command on the video: http://mediacast.sun.com/users/flippedbits/media/s10c-demo-jerry.swf when i installed solaris 10 in virtualbox, i opted for a zfs file system: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 # zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 9.27G 6.35G33K /rpool rpool/ROOT 3.51G 6.35G21K legacy rpool/ROOT/s10x_u8wos_08a 3.51G 6.35G 3.51G / rpool/dump 1.00G 6.35G 1.00G - rpool/export 3.77G 6.35G23K /export rpool/export/home 3.77G 6.35G 3.77G /export/home rpool/swap1G 7.35G16K - can i go back and re-install solaris 10 with a UFS and make this flar problem go away? i am only installing solaris 10 on virtualbox to create the branded zone so a re-install will work for me. Hi so flar create -L cpio -n myflash should work for you, but you need the -L cpio bit, ( or pax ), if you had a separate /var dataset you'd need to manually run cpio command. Enda Enda O'Connor x19781 Software Product Engineering Patch System Test : Ireland : x19781/353-1-8199718 ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
according to my notes, i create the flar with: #flar create -n myflash /export/home/s10-.flar i picked up the command on the video: http://mediacast.sun.com/users/flippedbits/media/s10c-demo-jerry.swf when i installed solaris 10 in virtualbox, i opted for a zfs file system: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 # zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 9.27G 6.35G33K /rpool rpool/ROOT 3.51G 6.35G21K legacy rpool/ROOT/s10x_u8wos_08a 3.51G 6.35G 3.51G / rpool/dump 1.00G 6.35G 1.00G - rpool/export 3.77G 6.35G23K /export rpool/export/home 3.77G 6.35G 3.77G /export/home rpool/swap1G 7.35G16K - can i go back and re-install solaris 10 with a UFS and make this flar problem go away? i am only installing solaris 10 on virtualbox to create the branded zone so a re-install will work for me. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
Jerry Jelinek wrote: xx wrote: i installed virtualbox and installed solaris 10 from an iso download. i used the flar command to create s10.flar as directed in: http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide i then tried to install s10.flar in the solaris 10 branded zone: init...@dogpatch:~# zoneadm -z csuite install -a /virtualbox/s10.flar -u WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. Log File: /var/tmp/csuite.install_log.2raajz Installing: This may take several minutes... Missing etc at /zones/csuite/root Missing etc/svc at /zones/csuite/root Missing var at /zones/csuite/root Missing var/svc at /zones/csuite/root Missing lib/svc at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Missing sbin/zonename at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Missing usr/bin/chmod at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Sanity Check: FAILED (see log for details). ERROR: Result: *** Installation FAILED *** init...@dogpatch:~# zonecfg -z csuite info zonename: csuite zonepath: /zones/csuite brand: solaris10 autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: shared hostid: net: address: 192.168.30.4 physical: vnic0_3 defrouter not specified init...@dogpatch:~# did i skip a step? How did you create the flar of the s10 system? Did the s10 system have a zfs root? If so, then you must create the flar using an explicit -L option to specify either a cpio or pax archive. Otherwise the flar will actually contain a zfs send stream of the root pool and that is not suitable for installing a zone (since the zone root must be a dataset, not a pool). I recently integrated the following bug fix to help address this: 6903478 need better error msg for flar made on system with zfs root Jerry Also if the system has a separate /var and is zfs root based, you will need to manually build the cpio archive, ie flar create -L cpio will not work. 6889459 flarcreate using cpio of a system running SUNWCreq zfs root with seperate /var fails. I used the following cd / find . \( \( -fstype nfs -o -fstype autofs \) -prune \) -o -print| egrep -v "^./proc|^./system|^./devices|^./dev|^./export/home|^./home|^./tmp" |cpio -oc > /export/home/oryx.cpio But that is only if you have zfs root and separate /var. Enda ___ zones-discuss mailing list zones-discuss@opensolaris.org -- Enda O'Connor x19781 Software Product Engineering Patch System Test : Ireland : x19781/353-1-8199718 ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
xx wrote: i installed virtualbox and installed solaris 10 from an iso download. i used the flar command to create s10.flar as directed in: http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide i then tried to install s10.flar in the solaris 10 branded zone: init...@dogpatch:~# zoneadm -z csuite install -a /virtualbox/s10.flar -u WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. Log File: /var/tmp/csuite.install_log.2raajz Installing: This may take several minutes... Missing etc at /zones/csuite/root Missing etc/svc at /zones/csuite/root Missing var at /zones/csuite/root Missing var/svc at /zones/csuite/root Missing lib/svc at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Missing sbin/zonename at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Missing usr/bin/chmod at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Sanity Check: FAILED (see log for details). ERROR: Result: *** Installation FAILED *** init...@dogpatch:~# zonecfg -z csuite info zonename: csuite zonepath: /zones/csuite brand: solaris10 autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: shared hostid: net: address: 192.168.30.4 physical: vnic0_3 defrouter not specified init...@dogpatch:~# did i skip a step? How did you create the flar of the s10 system? Did the s10 system have a zfs root? If so, then you must create the flar using an explicit -L option to specify either a cpio or pax archive. Otherwise the flar will actually contain a zfs send stream of the root pool and that is not suitable for installing a zone (since the zone root must be a dataset, not a pool). I recently integrated the following bug fix to help address this: 6903478 need better error msg for flar made on system with zfs root Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
there is no /zones/csuite as defined by the zonepath - doesn't install create this? -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] solaris 10 branded zone
i installed virtualbox and installed solaris 10 from an iso download. i used the flar command to create s10.flar as directed in: http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide i then tried to install s10.flar in the solaris 10 branded zone: init...@dogpatch:~# zoneadm -z csuite install -a /virtualbox/s10.flar -u WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed in the global zone. A ZFS file system has been created for this zone. Log File: /var/tmp/csuite.install_log.2raajz Installing: This may take several minutes... Missing etc at /zones/csuite/root Missing etc/svc at /zones/csuite/root Missing var at /zones/csuite/root Missing var/svc at /zones/csuite/root Missing lib/svc at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Missing sbin/zonename at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Missing usr/bin/chmod at /zones/csuite/root Is this a sparse zone image? The image must be whole-root. Sanity Check: FAILED (see log for details). ERROR: Result: *** Installation FAILED *** init...@dogpatch:~# zonecfg -z csuite info zonename: csuite zonepath: /zones/csuite brand: solaris10 autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: shared hostid: net: address: 192.168.30.4 physical: vnic0_3 defrouter not specified init...@dogpatch:~# did i skip a step? -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
On Tue, Dec 08, 2009 at 09:31:55AM -0800, xx wrote: > i'm still not doing something right: > > init...@dogpatch:~# pkg install SUNWs10brand > Creating Plan > pkg: The following pattern(s) did not match any packages in the current > catalog. > Try relaxing the pattern, refreshing and/or examining the catalogs: > SUNWs10brand > > init...@dogpatch:~# pkg info -r "*" 2>&1 | grep brand > pkg://development/SUNWipkg-brand > init...@dogpatch:~# pkg info -r "*" 2>&1 | grep s10 > init...@dogpatch:~# pkg publisher > PUBLISHER TYPE STATUS URI > development (preferred) origin online > http://pkg.opensolaris.org/dev/ > extra origin online > https://pkg.sun.com/opensolaris/extra/ > opensolaris.org origin online > http://pkg.opensolaris.org/release/ it's also a bug to be subscribed to both the "release" and the "dev" repos. you can't be running both an official release and a dev build at the same time. you need to remove the "release" repo. ed ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
you are right: init...@dogpatch:~# pkg info -r "*" 2>&1 | grep brand pkg://opensolaris.org/SUNWipkg-brand pkg://opensolaris.org/SUNWs10brand init...@dogpatch:~# pkg publisher PUBLISHER TYPE STATUS URI opensolaris.org (preferred) origin online http://pkg.opensolaris.org/dev/ development origin online http://pkg.opensolaris.org/dev/ extra origin online https://pkg.sun.com/opensolaris/extra/ release origin online http://pkg.opensolaris.org/release/ init...@dogpatch:~# holy smoke - i would have never figured that out - thanks for taking time to help me. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
On Tue, 08 Dec 2009 18:31:55 +0100, xx wrote: > i'm still not doing something right: > > init...@dogpatch:~# pkg install SUNWs10brand > Creating Plan > pkg: The following pattern(s) did not match any packages in the current > catalog. > Try relaxing the pattern, refreshing and/or examining the catalogs: > SUNWs10brand > > init...@dogpatch:~# pkg info -r "*" 2>&1 | grep brand > pkg://development/SUNWipkg-brand > init...@dogpatch:~# pkg info -r "*" 2>&1 | grep s10 > init...@dogpatch:~# pkg publisher > PUBLISHER TYPE STATUS URI > development (preferred) origin online > http://pkg.opensolaris.org/dev/ > extra origin online > https://pkg.sun.com/opensolaris/extra/ > opensolaris.org origin online > http://pkg.opensolaris.org/release/ > init...@dogpatch:~# I think thats because your publisher local name is not the default, I did the same today and it worked batsc...@osoldev:/usr/lib/brand$ pkg info -r "*" 2>&1 | grep brand pkg://opensolaris.org/SUNWipkg-brand pkg://opensolaris.org/SUNWs10brand my publisher is this: batsc...@osoldev:/usr/lib/brand$ pkg publisher PUBLISHER TYPE STATUS URI opensolaris.org (preferred) origin online http://pkg.opensolaris.org/dev/ blastwave origin online http://blastwave.network.com:1/ osol-contrib origin online http://pkg.opensolaris.org/contrib/ sunfreeware.com origin online http://pkg.sunfreeware.com:9000/ I believe there were some problems recently when the local name did not matched the "offical" publishers name. hth -- frankB It is always possible to agglutinate multiple separate problems into a single complex interdependent solution. In most cases this is a bad idea. ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
i'm still not doing something right: init...@dogpatch:~# pkg install SUNWs10brand Creating Plan pkg: The following pattern(s) did not match any packages in the current catalog. Try relaxing the pattern, refreshing and/or examining the catalogs: SUNWs10brand init...@dogpatch:~# pkg info -r "*" 2>&1 | grep brand pkg://development/SUNWipkg-brand init...@dogpatch:~# pkg info -r "*" 2>&1 | grep s10 init...@dogpatch:~# pkg publisher PUBLISHER TYPE STATUS URI development (preferred) origin online http://pkg.opensolaris.org/dev/ extra origin online https://pkg.sun.com/opensolaris/extra/ opensolaris.org origin online http://pkg.opensolaris.org/release/ init...@dogpatch:~# -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] solaris 10 branded zone
On 12/ 7/09 04:19 PM, xx wrote: i am following the zonecfg script at the bottom of: http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide however i fail to create the SUNWsolaris10 zone: init...@dogpatch:~# uname -a SunOS dogpatch 5.11 snv_128a i86pc i386 i86pc init...@dogpatch:~# zonecfg -z xx xx: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:xx> create -t SUNWsolaris10 SUNWsolaris10: No such zone configured zonecfg:xx> info xx: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:xx> what am i doing wrong? I forgot to include a step in the developer guide: You have to install SUNWs10brand first: ---8<--- # pkg install SUNWs10brand ---8<--- I apologize for not including this step. I thought that the brand's files would be installed by default. Thanks for pointing this out! I'll update the guide immediately. Jordan ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] solaris 10 branded zone
i am following the zonecfg script at the bottom of: http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide however i fail to create the SUNWsolaris10 zone: init...@dogpatch:~# uname -a SunOS dogpatch 5.11 snv_128a i86pc i386 i86pc init...@dogpatch:~# zonecfg -z xx xx: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:xx> create -t SUNWsolaris10 SUNWsolaris10: No such zone configured zonecfg:xx> info xx: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:xx> what am i doing wrong? -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
