On May 18, 2011, at 10:32 AM, Darren J Moffat wrote: > On 05/18/11 16:57, Luca Ferrari wrote: >> I'm not sure what "private" means, but am I supposed to be NOT able to >> create, for instance, my person zfs explorer writing a from-scratch C >> program? > > Private means it isn't documented or a committed interface for people outside > of the project itself to write to.
Previously private interfaces have been known to become committed and public. > So no you aren't supposed to be able to write 3rd party tools and link them > against the libzfs API. This is just a matter of risk management. In the open source (eg illumos) world, it is easy to follow changes in the API. As long as the work involved is known, a decision can be justified. -- richard _______________________________________________ zfs-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-code
