On 02/23/10 07:23 PM, Kendall Tatum wrote: >> The text installer provides slice manipulation as a method for >> coexistence with existing UFS installations (and as a way to >> divvy up the disk on SPARC systems). >> >> /var and /opt can be managed via ZFS after the install >> completes. >> Currently, they are folders on the boot filesystem >> (rpool/ROOT/opensolaris at first install). > > So if I want to put them on their own filesystem on another drive, I will > need to copy their contents to a new location after install. Thanks for the > info. It has helped me a lot. I am learning with everything I try, that > OpenSolaris is truly a different beast from the SunOS 5.9. >
No, you cannot put them in their own file system on another drive. These file systems are part of the boot environment and must remain in the root ZFS pool in order for future package operations to work correctly. Creating alternate file systems *within the same ZFS pool* can work, but is an entirely manual process and we don't make any guarantees about it working at this point. >> There's no >> need for var and opt to be on a separate slice from >> the root install. > > For desktop stuff, one filesystem is fine, but for a busy mail server I can > not see that being practical. How would you control setuid stuff or keep a > mail queue from filling up root without the ability to put /var (or its > subdirectories) on their own filesystem or slice? Quotas are part of the answer (in terms of disk space consumption). How /var will be handled is currently a topic of discussion, the setuid aspect is one thing being considered. However, since you're new to OpenSolaris and ZFS, I'd encourage taking some time to get familiar with the system before trying to extensively customize as some assumptions from the UFS world, especially about slicing, no longer apply. Dave
