On Mon, Oct 07, 2013 at 10:51:26AM -0700, Matthew Ahrens wrote:
> Agreed! As we consider creating a platform-independent codebase for
Received: from [91.121.88.72] (helo=mail.dawidek.net)
by node002.open-zfs.net
with esmtp (HybridCluster distributed mail proxy)
(envelope-from <[email protected]>); Mon, 07 Oct 2013 18:43:47 -0000
> OpenZFS, we will need to define what interfaces it is allowed to use.
> Something like libzpool's zfs_context.h + kernel.c, but less hacky.One of the hard parts I recall from my work was GFS and using it for .zfs/ directory. There were countless bugs with stuff like '..' directory (accessed locally and through NFS), automounting snapshots, etc. Some nice properties of .zfs/ were impossible to implement on FreeBSD. For example rmdir(2) being equivalent of destroying a snapshot, because in FreeBSD we deny in VFS above ZFS rmdir(2) on a mountpoint. All in all being able to simplify GFS would help a lot with ZFS portability. I remember ZFS-on-FUSE implementation didn't have .zfs/ support (probably for other reasons too). The same for initial MacOS X port. I'm sorry for not volunteering, but if someone is looking for things to work on here it is:) -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://mobter.com
pgpXlmJCWo8gR.pgp
Description: PGP signature
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
