site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On May 2, 2005, at 11:17 AM, Nicolas Berloquin wrote: Hello ! You seen the following (note the VFS section)...? -Shawn _______________________________________________ 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... This email sent to site_archiver@lists.apple.com I'm new to the list, but I saw a few familiar names posting here ;D I've searched the archives about blocking writes (or other accesses) on a storage device and found some suggestions like : 1 - use a stacked nullfs-like driver and call the 'super' methods. 2 - never use a stacked driver... ever 3 - the docs on vfs say that vfs are going to change, so don't use that. (even at todays' date, ie after tiger release.) Since the docs on developer.apple.com haven't been updated for tiger, I'm wondering what the current state of affair is about all that. Is is still verboten to use nullfs-like techniques ? Will apple implement an NKE type of API, FSKE with usable hooks ? thanks for any pointers or hints ^_^ <http://developer.apple.com/documentation/Darwin/Reference/ KPI_Reference/kpi_reference.html> Also on Apple ADC downloads (log into ADC account, may require a seed key) you can find a set of file system plugin samples. Anyway what exactly do mean by blocking writes? What are you trying to achieve? smime.p7s