site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Thanks for the gun, I promise I won't shoot myself in the foot. ;-) On Nov 20, 2007, at 5:05 AM, Quinn wrote: In that case I would just write it to a file (-: _______________________________________________ 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... Now, is there any documentation on these interfaces? A google on vnode_open returns very few results... Kynan It's not that you /can't/ read or write files from the kernel, it's that doing this exposes you to all sorts of crazy deadlock situations. In this case, you're sitting at the block driver level and you end up calling all the way back up to the VFS level. It's very easy to deadlock due to reentrancy. It's also easy to deadlock due to lack of resources. OTOH, for a research project you should be able to make it work. You can get the vnode for a path using vnode_lookup. You can open it using vnode_open. And you can write to it using VNOP_WRITE. You don't even have to take a dependency on the kernel; these are all KPIs. This email sent to site_archiver@lists.apple.com