On 16/04/10 07:50 PM, Ethan Quach wrote:
On 04/16/10 19:39, Darren Reed wrote:
So I would do...
<ai_target_device>
c0t0d0
<target_device_install_slice_number>
3
</target_device_install_slice_number>
<ai_target_device>
To install into c0t0d0s3?
It would be
<ai_target_device>
<target_device_name>
c0t0d0
</target_device_name>
<target_device_install_slice_number>
3
</target_device_install_slice_number>
</ai_target_device>
Is this available with build 136?
Yes, that tag has been there since the beginning.
Is there also a way to name the pool or does that
still need to be "rpool"? Even if there are multiple
rpool's, I think it numbers them to avoid conflicts,
right?
Actually no, the text-installer auto names the pool
with "rpool[N+1]", given the existence of "rpool[N].
But AI currently will always use "rpool". Meaning
that after installation, you won't readily be able to
import your other rpool if that's what you have on
your system. You'd have to rename it to import it,
(and if you have bootable ZFS BEs on there, make
sure you update that pool's grub menu, bootfs
property, and all of your BEs' entries in /etc/vfstab
if you've got any legacy mounted zfs datasets.)
Ok, so I can mix-n-match with one install of opensolaris
and nevada/s10, but I have to wait a while longer before
I can easily mix-n-match different installs of opensolaris.
Darren
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
