12278 nfs-zone needs man page changes
Reviewed by: Peter Tribble <peter.tribble@gmail.com>
Reviewed by: Gordon Ross <gordon.w.ross@gmail.com>

*** 147,156 ****
           overlapping id spaces, the inbound attribute string could potentially
           be mapped to the wrong id.  However, this is not functionally
           different from mapping the inbound string to nobody, yet provides
           greater flexibility.
  
  SEE ALSO
       lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
!      sharectl(1M), smf(5)
  
! illumos                        December 18, 2016                       illumos
--- 147,165 ----
           overlapping id spaces, the inbound attribute string could potentially
           be mapped to the wrong id.  However, this is not functionally
           different from mapping the inbound string to nobody, yet provides
           greater flexibility.
  
+ ZONES
+      NFS can be served out of a non-global zone.  All of the above
+      documentation applies to an in-zone NFS server.  File sharing in zones is
+      restricted to filesystems a zone completely controls.  Some zone brands
+      (see brands(5)) do not give the zone's root its own filesystem, for
+      example.  Delegated ZFS datasets to a zone are shareable, as well as
+      lofs-remounted directories.  The zone must have sys_nfs privileges; most
+      brands grant this already.
+ 
  SEE ALSO
       lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
!      sharectl(1M), brands(5), smf(5), zones(5)
  
! illumos                        February 4, 2020                        illumos