After longtime I did some changes to hdinstaller in belenix
Added new screens to create an additional user,
Install grub option to MBR or primary partition
and ZFS support for creating home slice.

We plan to extend this so that user can be able to create many zfs partitions.
The idea is provide user an option whether he wants ufs or zfs.
If user chooses zfs, then root slice (ufs) is created and an optional swap and rest all will be one zfs pool and let the user create as many zfs slices as he needs. I don't know how I am gonna do it, but this is the idea in future.

But for the timbeing if user chooses to have a /home partition,
user will be asked whether he wants it to make a zfs part.
If yes it simply creates a zpool and creates a zfs filesystem and set the mount point to /export/home.
Very simple right...but we faced some serious problem , spent 2 days time on this and Belenix 0.5 got delayed as well.
The problem is when we create a zpool in alternate root it creates the pool properly, but mount point value is messed up.
For testing, I created a testfile with which I can create a zpool over it.
mkfile -m 65m /tmp/poolfile
Then we tried our zpool command...
zpool create -R /mnt/newroot /tmp/poolfile
Myself, Moinak and Kishore were debugging the issue for 2 days, we took truss o/ps, enabled dtrace probes in libzfs, fbt and found that the zfs_is_mountable() gets some corrupted mountpoint string.
No clue why its happening, because the property
ZFS_PROP_MOUNTPOINT is set properly.
But when zfs_is_mountable() calls zfs_prop_get() some junk value is appearing.
fortunately Kishore got a build 48 box. We tried out there and its not appearing. :-O
But surprisingly it only appears in the BeleniX only.
we copied the zfs module, from build 48 box, and tested...it works!
Then we realized that Moinak actually got the pre-release sources ratherthan
the build 48 sources. It seems some last minute bugfixes have gone-in which
fixes this issue. So Moinak downloaded the latest snapshot again and built
only the zfs module and I quickly copied the module to my box.
I tested and it worked fine.
We ended up doing almost a code walkthrough.
I tested my installer and it also worked fine.
We later searched in opensolaris.org to find out
that 2 important bug fixes have gone-in
6469385 zfs_set_prop_nvlist range checking is busted
6469830 'zfs set' panics non-debug systems
chkout this thread:
http://www.opensolaris.org/jive/thread.jspa?messageID=59798&#59798