site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Hi, Best regards, Anton JP On Apr 30, 2007, at 5:41 AM, Shailesh Parulekar wrote: Firstly,Thanks all for extending your help. Thanks again, --shailesh parulekar From: Michael Smith <drivers@mu.org> To: Shailesh Parulekar <smileyshailoo@hotmail.com> CC: darwin-kernel@lists.apple.com Subject: Re: Info needed for File System Development Date: Sun, 29 Apr 2007 14:43:39 +0930 On Apr 26, 2007, at 6:13 PM, Shailesh Parulekar wrote: What are the "needs of your product"? -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ _______________________________________________ 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... On 30 Apr 2007, at 23:33, John Davidorff Pell wrote: This sounds much like you're trying to add full journaling to HFS+. Is this a fair characterisation? I don't think so. He is effectively describing what Leopard's Time Machine or Legato's Networker backup solution provide (implemented differently) so they seem to be reinventing the wheel somewhat... I.e. you keep all changes to the file so you can go back in time to any particular version of the file that previously existed. So for example when you delete a file or it gets corrupt or when you simply modify a file and don't like the changes you can then get back the previous version(s) at will at the simple click of a button or two... About, need of our product:: At a very high level, I wish to intercept the I/Os (essentially Writes) made to a set of files and store the changes in my secondary storage so that in the event of machine crash user should be able to reconstruct his/her files with the help of the product. In general terminology it is Continuous Data Protection (C.D.P.) My intention is to track the block changes that happen to the files and have my meta data pointing to the old (changed) blocks so that I get to construct various versions of the files from my meta data. As and when plans are crystallized I will have more concrete questions to chalk down. For now I just need to get started with the Mac OS X Internals and think of possible avenues to meet my requirements. I need to develop a Filter driver to plug-in into the MAC File System in order to 'filter' the read/writes to the files and process the same as per the need of our product. = Mike This email sent to site_archiver@lists.apple.com