site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Le 6 oct. 08 à 13:23, Karan, Cem (Civ, ARL/CISD) a écrit : On Thu, Oct 2, 2008 at 4:07 PM, Karan, Cem (Civ, ARL/CISD) <CKaran@arl.army.mil> wrote: I've been poking around, trying to find more information on Apple's implementation of VFS, but haven't been able to find much. Is it still supported? Should I use something else? Searching for "VFS" on developer.apple.com gives this as the first result: What I would like to do (assuming I have any free time): I think you may considere using Mac Fuse for this purpose. http://code.google.com/p/macfuse/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... http://developer.apple.com/qa/qa2001/qa1242.html I'm sorry, I wasn't clear in my earlier message. I saw that, and read it before, including the following: "Documentation for the VFS KPI is still rather rudimentary. Apple will rectify this in the future (r. 3524590); in the meantime, this Q&A includes a list of references to documentation and other resources." I have the 4.4 BSD book, and am reading through it, I googled for VFS KPI, and got lots of hits for other systems, as well as for the book MAC OS X Internals By Amit Singh, but I haven't seen much about the KPI. What I'm really after is complete documentation on how the KPI works, so I can decide if it is the right path to go down. I want to write an interface to my version control system (in this case, Subversion, but it could be anything) that lets me 'mount' different working copies (and different revisions of the same one), in the same way that you can mount a disk image. The idea is that the meta information (.svn, .cvs, whatever) can be fully hidden from the mounted drive. Each modification can be an unnamed revision, with some kind of special tool handling naming particular modifications (or, if I can, I can make it like how CDs/DVDs have a burn button in their toolbar, I haven't fully thought out the interface yet). Tools that don't understand what version control is wouldn't break the system, and using it would be more natural. There is a well defined Obj-C and C API. And you can also read Mac FUSE sources to know how to write a native file system. The author of this project is Amit Singh. This email sent to site_archiver@lists.apple.com