Solaris 10 10/08 と Nevada b101 の zoneadm

ちょっ、小室せんせー、なにやってんすかぁー！！！！
というわけで、全然関係ありませんが、本日朝一番の衝撃だったわけで何となく書いてみたり。

ちなみに、昨夜、一番下の妹から「結納の日付が決まりました」とメールが。
以前にも、ここに書いたのですが・・・某スレにお祝いの言葉を書き込んでくれた人がいました・・・（遠い目
そんなあなたにも報告です(｀・ω・´)ゞビシッ!!

未経験な兄を差し置いて 2 回目の結納とか、もう、あｓｂづ「えおｑふぉえｗ」ｆｐｌ；


で、zoneadm のことが気になったので、Solaris 10 10/08 と Nevada b101 の binary を比べてみた。

 # mcs -p /usr/sbin/zoneadm
/usr/sbin/zoneadm:

@(#)SunOS 5.11 snv_101 November 2008

# strings /usr/sbin/zoneadm | grep -i zfs
could not restore zonepath, the zfs mountpoint is set as:
.zfs
cd %s && /usr/bin/find . -type s -prune -o -depth -print | /usr/bin/egrep -v '^\./\.zfs$|^\./\.zfs/' | /usr/bin/cpio -pdmuP@ %s > %s 2>&1
could not restore zonepath, the zfs mountpoint is set as:
.zfs
cd %s && /usr/bin/find . -type s -prune -o -depth -print | /usr/bin/egrep -v '^\./\.zfs$|^\./\.zfs/' | /usr/bin/cpio -pdmuP@ %s > %s 2>&1
can be used to specify the name of a ZFS snapshot that was taken from
instead of creating a new ZFS snapshot.  All other arguments are passed
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).
failed to initialize ZFS library
could not verify fs %s: zfs '%s' mountpoint is not "legacy"
could not verify fs %s: could not access zfs dataset '%s'
cannot verify zfs dataset %s: volumes cannot be specified as a zone dataset resource
could not verify zfs dataset %s: mountpoint cannot be inherited
could not verify zfs dataset %s: %s
could not verify zfs datasets: unable to enumerate datasets
The ZFS file system for this zone has been destroyed.
A ZFS file system has been created for this zone.
cannot mount ZFS dataset %s: %s
cannot create ZFS dataset %s: %s
cannot create ZFS dataset %s: out of memory
Instead of copying, a ZFS clone has been created for this zone.
preventing use of a ZFS clone.
%s/.zfs/snapshot/%s
could not remove the software inventory from ZFS clone %s
could not mount ZFS clone %s
could not create ZFS clone %s: out of memory
cannot verify zfs dataset %s: volumes cannot be specified as a zone dataset resource
clone [-m method] [-s <ZFS snapshot>] [brand-specific args] zonename
clone [-m method] [-s <ZFS snapshot>] [brand-specific args] zonename
clone [-m method] [-s <ZFS snapshot>] [brand-specific args] zonename
clone [-m method] [-s <ZFS snapshot>] [brand-specific args] zonename
clone [-m method] [-s <ZFS snapshot>] [brand-specific args] zonename

ちゃんと入ってますね(｀・ω・´)
zonecfg で、zonepath を /rpool/testzone みたいな感じで pool の直下に指定(当然、rpool/testzone なんて filesystem はない状態)することで、zoneadm -z testzone install なんてすると、 A ZFS file system has been created for this zone. というメッセージが出て、zfs create を内部で実行し、 zone の root が rpool/testzone なんて状態になって zoneadm で clone や snapshot とったりできるのですが・・・

Solaris 10 10/08 の zoneadm を見ると、
--

$ mcs -p /usr/sbin/zoneadm
/usr/sbin/zoneadm:

@(#)SunOS 5.10 Generic 137138-09 Sep 2008

$ strings /usr/sbin/zoneadm | grep -i zfs
%s/.zfs
failed to initialize ZFS library
cd %s && /usr/bin/ls -A | /usr/bin/egrep -v '^\.zfs$' | /usr/bin/xargs /usr/bin/rm -rf
cd %s && /usr/bin/find . -type s -prune -o -depth -print | /usr/bin/egrep -v '^\./\.zfs$|^\./\.zfs/' | /usr/bin/cpio -pdmuP@ %s > %s 2>&1
cannot verify zfs dataset %s: volumes cannot be specified as a zone dataset resource
could not verify zfs dataset %s: mountpoint cannot be inherited
could not verify zfs dataset %s: %s
could not verify zfs datasets: unable to enumerate datasets
cannot verify zfs dataset %s: volumes cannot be specified as a zone dataset resource
could not verify fs %s: zfs '%s' mountpoint is not "legacy"
could not verify fs %s: could not access zfs dataset '%s'

これだけ・・・( ´・ω・｀)
どうも、さとうの勘違いくさい。
単に、ZFS 状に zone の / を置いても LiveUpgrade とかできるようになったよ。ということらすぃ。。。