Re: [zones-discuss] Native Vs. ipkg

2010-02-18 Thread Frank Batschulat (Home) 
On Thu, 18 Feb 2010 16:45:01 +0100, Ben ben.lav...@gmail.com wrote:

 What are the differences between native and ipkg zones?
 When I did one of the Solaris 10 admin courses we learnt how zones use parts 
 of the global-zone (for example using global-zone directories like /etc 
 etc...).

That is one of the differences, you are refering to what we called 'sparse 
root' zones
which inherit a lof ot the system stuff like /etc , /dev, /usr via lofs 
loopback file system mounts.
this was possible with Solaris 10 and the so called 'native' branded zones.

this is different for OpenSolaris ipkg branded zones, which does only support
'whole root zones'.

and of course as already mentioned, the IPS vrs SysV packaging difference.

hth
frankB

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zoneadm clone -m copy does not really copy on ZFS zonepath

2010-02-18 Thread Frank Batschulat (Home) 
On Thu, 18 Feb 2010 19:58:11 +0100, Christine Tran christine.t...@gmail.com 
wrote:

 On Sat, Feb 13, 2010 at 3:10 AM, Frank Batschulat (Home)
 frank.batschu...@sun.com wrote:

 a '-x nodataset' option for 'clone' like in 'install' is unlikely going to 
 happen, in
 fact I will remove the '-x nodataset' option for 'install' completely soon 
 in OSOL build 135
[...]
 I have created test ipkg type zones on this laptop before, I have not
 done an upgrade but I've allowd Package Manager to update packages as
 far as it's abled.  You say you will remove -x nodataset option,
 implying it hasn't been done yet, but here's what happened this

the '-x nodataset' option does only apply to the 'native' brand (ie. Solaris 
10, SX-DE)
(see native(5)) - it is not available to the 'ipkg' brand nor is it available
for the solaris8, solaris9 and solaris10 brands.

 morning when I tried to create a new zone.

 r...@fiat~ cat /etc/release
OpenSolaris 2008.11 snv_101b_rc2 X86
Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.
 Use is subject to license terms.
Assembled 19 November 2008

 r...@fiat~ zonecfg -z pink
 pink: No such zone configured
 Use 'create' to begin configuring a new zone.
 zonecfg:pink create
 zonecfg:pink set zonepath=/zone/pink
 zonecfg:pink add net
 zonecfg:pink:net set physical=e1000g0
 zonecfg:pink:net set address=192.168.20.1/24
 zonecfg:pink:net end
 zonecfg:pink verify
 zonecfg:pink commit
 zonecfg:pink info
 zonename: pink
 zonepath: /zone/pink
 brand: ipkg
 autoboot: false
 bootargs:
 pool:
 limitpriv:
 scheduling-class:
 ip-type: shared
 net:
   address: 192.168.20.1/24
   physical: e1000g0
   defrouter not specified
 zonecfg:pink exit
 r...@fiat~ zoneadm -z pink install -x nodataset
 Error: no zonepath dataset.

thats one of the problems that may arise, since the
'-x nodataset' option is really handled inside zoneadm.c:install_func()
and not in the brand specific code that is executed later.

zoneadm did honoured this option, but the 'ipkg' brand
specific code that will be executed _after_ zoneadm.c:install_func()
barfs.

 OK, I will create a dataset:

 r...@fiat~ zfs list
 NAME  USED  AVAIL  REFER  MOUNTPOINT
 rpool26.4G  71.5G72K  /rpool
 rpool/ROOT   19.8G  71.5G18K  legacy
 rpool/ROOT/opensolaris   19.8G  71.5G  19.6G  /
 rpool/dump   1.97G  71.5G  1.97G  -
 rpool/export 2.70G  71.5G19K  /export
 rpool/export/home2.70G  71.5G19K  /export/home
 rpool/export/home/ctran  2.70G  71.5G  2.70G  /export/home/ctran
 rpool/swap   1.97G  73.5G  3.81M  -
 r...@fiat~ zfs create rpool/pink
 r...@fiat~ zfs set mountpoint=/zone/pink rpool/pink
 r...@fiat~ zfs list
 NAME  USED  AVAIL  REFER  MOUNTPOINT
 rpool26.4G  71.5G74K  /rpool
 rpool/ROOT   19.8G  71.5G18K  legacy
 rpool/ROOT/opensolaris   19.8G  71.5G  19.6G  /
 rpool/dump   1.97G  71.5G  1.97G  -
 rpool/export 2.70G  71.5G19K  /export
 rpool/export/home2.70G  71.5G19K  /export/home
 rpool/export/home/ctran  2.70G  71.5G  2.70G  /export/home/ctran
 rpool/pink 18K  71.5G18K  /zone/pink
 rpool/swap   1.97G  73.5G  3.81M  -

 Try to install again

 r...@fiat~ zoneadm -z pink uninstall
 Are you sure you want to uninstall zone pink (y/[n])? y
 cannot open 'rpool/pink/ROOT': dataset does not exist
 Error: no active dataset.
 cannot open 'rpool/pink/ROOT': dataset does not exist
 cannot open 'rpool/pink/ROOT': dataset does not exist
 cannot open 'rpool/pink/ROOT': dataset does not exist
 Error: destroying ZFS dataset.

more follow up problems that result from the fact that
zoneadm honoured the '-x nodataset' option when it really must not.

---
frankB
___
zones-discuss mailing list
zones-discuss@opensolaris.org

[zones-discuss] zone preconfiguration via sysidcfg fails on osol-b132

2010-02-18 Thread Bruno Damour 
Hello
I'm creating a zone and after install, copying a sysidcfg.
On zone boot and zlogin -C I still run into the prompts.
My sysidcfg is :

keyboard=French
system_locale=en_US.UTF-8
terminal=xterms
network_interface=primary {
dhcp 
protocol_ipv6=yes
}
security_policy=kerberos {
default_realm=RUOMAD.LOCAL
admin_server=rebma.ruomad.local
kdc=rebma.ruomad.local
}
name_service=DNS {
 domain_name=ruomad.local
 name_server=192.168.0.150,192.168.0.1
}
nfs4_domain=dynamic
timezone=Europe/Paris
root_password=fto/dU8MKwQRI

what can be wrong ?
PS : it used to work on previous SXCE builds

Thanks in advance
Bruno
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone preconfiguration via sysidcfg fails on osol-b132

2010-02-18 Thread Edward Pilatowicz 
On Thu, Feb 18, 2010 at 05:14:48PM -0800, Bruno Damour wrote:
 Hello
 I'm creating a zone and after install, copying a sysidcfg.
 On zone boot and zlogin -C I still run into the prompts.
 My sysidcfg is :

 keyboard=French
 system_locale=en_US.UTF-8
 terminal=xterms
 network_interface=primary {
 dhcp
 protocol_ipv6=yes
 }
 security_policy=kerberos {
 default_realm=RUOMAD.LOCAL
 admin_server=rebma.ruomad.local
 kdc=rebma.ruomad.local
 }
 name_service=DNS {
  domain_name=ruomad.local
  name_server=192.168.0.150,192.168.0.1
 }
 nfs4_domain=dynamic
 timezone=Europe/Paris
 root_password=fto/dU8MKwQRI

 what can be wrong ?
 PS : it used to work on previous SXCE builds


one possibility is that opensolaris uses a different shadow file
password format (sha256 has i believe).  the hash'ed password you have
listed above (which you probably shouldn't include in an email ;) looks
like an old solaris style password (crypt(3c) perhaps).

ed
___
zones-discuss mailing list
zones-discuss@opensolaris.org