site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Bergstrand <http://www.bergstrand.org/brian/> PGP Key ID: 0xB6C7B6A2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD7jSfedHYW7bHtqIRApeLAKDaEbK7lhHQTdDl+4Ym8hkWYA534ACdHeb/ IO8DwLm+URmSbspo1L3kZl0= =dk9Q -----END PGP SIGNATURE----- _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... Since the knote interface is no longer public, does this mean that knotes are auto-generated by the kernel? This is for a local file system, but I'd be interested the status for network file systems too. I had a quick look at the VFS source and didn't see anything to suggest this is the case, but thought maybe the new kernel event system generated corresponding knotes. Then again, both HFS and UFS still generate their own notes... If knotes are not auto-generated, is there a way for VFS plugins to do so while still remaining KPI compliant? Knotes and byte-range locking (vfs_setlocklocal) seem to be some rather big oversights in the KPI. This email sent to site_archiver@lists.apple.com