-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lori Alt wrote:
>> The SXCE code base really only supports BEs that are
>> either all in one dataset, or have everything but /var in
>> one dataset and /var in its own dataset (the reason for
>> supporting a separate /var is to be able to set a set a
>
On 11/08/08 15:24, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any advice?. Suggestions/alternative approaches welcomed.
One obvious question - why?
Two reasons:
The SXCE code base really only supports BEs that are
either all in one dataset, or have ever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Any advice?. Suggestions/alternative approaches welcomed.
> One obvious question - why?
Two reasons:
1. Backup policies and ZFS properties.
2. I don't have enough spare space to "rejoin" all system slices in a
single one.
I thinking in messing w
Jesus Cea wrote:
> Hi, everybody.
>
> I just trying to upgrade my Solaris 10 Update 6 from UFS to ZFS. But I
> want to keep different portions of the OS in different ZFS datasets,
> just like I was doing until now. For example, my script to upgrade from
> Update 5 to Update 6 was:
>
> """
> [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, everybody.
I just trying to upgrade my Solaris 10 Update 6 from UFS to ZFS. But I
want to keep different portions of the OS in different ZFS datasets,
just like I was doing until now. For example, my script to upgrade from
Update 5 to Update 6 was
