site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Jun 4, 2007, at 11:03 PM, Terry Lambert wrote: -Mike _______________________________________________ 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... For a backup utility, you'd be much better off being an fsevents clients (search on <http://developer.apple.com>), and then reacting to events only for files which are actually changed since the last backup. Really?? Is this a change in policy? I had a mental post-it on fsevents that it was akin to an SPI and not really meant for general 3rd party use. My biggest beef with my present backup approach is how glacially slow it is comparing its catalog data to the disk in search of what's changed. What you describe sounds like a very efficient way to avoid all that work. This email sent to site_archiver@lists.apple.com