> On 4/12/06, Darren J Moffat <[EMAIL PROTECTED]> wrote:
>> So why not have /export/zfs_0/
>>                 /export/zfs_0/jumpstart
>>                 /export/zfs_0/jumpstart/s10
>>                 /export/zfs_0/jumpstart/s10/SXCRb35
>>
>> all as separate ZFS filesystems, they are cheap after all :-)
>
> It is still a bug which should be fixed. The requirement that only the
> base of a ZFS file system can be shared is a serious limitation which
> will hamper or even prevent deployment of ZFS at large sites.
> Simplified example: Someone may want to set up shares temporarily in a
> sub directory and the requirement to create an extra ZFS file system
> for that is a overkill, if not even a risk for production usage (I
> consider changes in a file system setup as a far higher risk than
> letting people share their data via NFS).
>

In this case I simply edited the /etc/dfs/dfstab file and shared out the
jumpstart area manually as per usual.  The old Solaris 8
"add_install_client" script failed anyways as it was unable to determine if
the local ZFS filesystem was in fact local.

I simply moved it to another old fashioned UFS filesystem ( yeah, I just
said old fashioned ) and then life went on as usual.

Shame that I could not run the necessary processes out of the ZFS filesystem
easily.  I wanted to have every rev from Sol8HW4 up to latest Nevada shared
out and bootable.  Oh well ...

-- 
Dennis Clarke

_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to