I'm not sure why you want to separate out all these filesystems on a root disk these days? The reason I recall needing to do it over a decade ago, was because disks were so small and perhaps you couldn't FIT /opt onto the same disk with /usr. So you needed to be able to say /usr is on this disk and /opt is over here on another one.
Perhaps it would be good if you explained the need for all these filesystems? If you have apps that need a lot of space, they can have their own filesystems created after the OS is installed. Like your /joker for instance, just do a zfs create for that after the OS install. This is my profile: # #cluster This tells what cluster of packages to install. # SUNWCXall is Entire Solaris Software Group Plus OEM Support. # SUNWCall is Entire Solaris Software Group. # SUNWCprog is Developer Solaris Software Group. # SUNWCuser is End User Solaris Software Group. # SUNWCreq is Core System Support Software Group. # SUNWCrnet is Reduced Network Support Software Group. install_type initial_install pool rpool auto auto auto mirror c1t0d0s0 c1t1d0s0 bootenv installbe bename zfsroot dataset /var system_type standalone cluster SUNWCXall For applications which need a little space that is tightly managed to not impact other applications running on the same system, like scratch/tmp/lock-files which might go nuts, I just give them a piece of the TMPFS filesystem and set a limit on it's size in /etc/vfstab: swap - /var/imap-proc tmpfs - yes size=512m swap - /var/imap-socket tmpfs - yes size=512m swap - /var/imap-log tmpfs - yes size=512m This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
