site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On May 16, 2005, at 8:50, Alexey Proskuryakov wrote: On 16.05.2005 16:24, "Dan Smith" <d_smith@ecrm.com> wrote: If this is truly a bug, and one that is likely to bite more than a very small number of people, our best strategy is to wait for Apple to fix it. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for General Semantics -------- Some people have a mental horizon of radius zero, and call it their point of view. -- David Hilbert -------- _______________________________________________ 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... I was hoping that someone on this list might know more about what's going on "under the hood" and might have a plausible explanation for what changed in 10.4 and how it is possible to get a sequence of events in which a) a file is deleted on the remote system, b) is SEEN as not existing any more on the local system, but c) gets an error when the local system attempts to rename a file to the now-available name of the deleted file. FWIW, last August I reported how a file can be deleted via SMB, and still be seen as existing on the same (!) local system (rdar://3749257). It's still not fixed, so looks like Apple is not very interested in such issues. It seems like a stretch to say that, because your favorite bug isn't fixed, Apple isn't interested. I've always found them to be interested, but often there are higher priority issues to deal with. This email sent to site_archiver@lists.apple.com