Ivan Buetler wrote:
Jerry, Thank you for your response. See my zonecfg of the named NGZ here:
[EMAIL PROTECTED] ~ # zonecfg -z named export
create -b
set zonepath=/zpool/zones/named
set autoboot=true
add inherit-pkg-dir
set dir=/lib
end
add inherit-pkg-dir
set dir=/platform
end
add inherit-pkg-dir
set dir=/sbin
end
add inherit-pkg-dir
set dir=/usr
end
add fs
set dir=/zpool/applic/bind-9.3.2-P1
set special=/zpool/applic/bind-9.3.2-P1/
set type=lofs
add options ro
add options nodevices
end
add fs
set dir=/zpool/data/named
set special=/zpool/data/named
set type=lofs
add options rw
add options nodevices
end
add net
set address=1.2.3.4/27
set physical=qfe3
end
add net
set address=21.2.3.5/27
set physical=qfe3
end
add net
set address=10.10.10.10/24
set physical=qfe4
end
add attr
set name=comment
set type=string
set value="Zone named"
end
It looks like you won't be able to upgrade. Assuming /zpool
is the mount of your zfs zpool, then your zonepath is on a
zfs dataset so this is the exact issue that upgrade cannot
handle yet. If you were to place your zones on a UFS filesystem
then the other fs entries you have to mount zfs datasets
within the zone would be fine.
Jerry
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
