On 04/16/10 19:50, 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.)
Oh and btw, beadm doesn't support BE across
multiple pools yet, so don't expect that to work.
It will appear to work (i.e. 'beadm list' will show
BEs from both pools), but there are gaps in the
other subcommands so I'd just avoid trying to use
it to manipulate something off the current pool.
-ethan
-ethan
Darren
On 16/04/10 05:46 PM, Ethan Quach wrote:
This is possible with AI as well. You can specify the
specific slice you want used to create the root pool
from by using the following (not very elegant tag
name right now, but...)
<ai_target_device>
....
...
..
<target_device_install_slice_number>
X
</target_device_install_sice_number>
</ai_target_device>
-ethan
On 04/16/10 15:37, Mary Ding wrote:
Darren:
You should be able to use the text installer to do this.
On 04/16/10 15:24, Darren Reed wrote:
What's the status of being able to specify a single slice
in a Solaris partition as the zfs pool to install Opensolaris
into with AI?
Just yesterday I had to uninstall opensolaris and install
nevada so that I could dual boot a box internally with S10
for testing...:-(
Darren
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
