From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ronald G Minnich To: <9fans@cse.psu.edu> Subject: Re: [9fans] Ephase question. In-Reply-To: <859eea04603e722a7dabc2bc0ef5bf73@plan9.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Date: Tue, 13 Aug 2002 00:05:11 -0600 Topicbox-Message-UUID: db550786-eaca-11e9-9e20-41e7f4b1d025 On Tue, 13 Aug 2002, Russ Cox wrote: > > I haven't seen a version of unix do this one for a while (as in decades). > > The remove succeeds, the file goes away when the last reference does (but > > you have to have inodes ...). But maybe there is some version of Unix > > you're referencing I'm not familiar with -- there's a lot of possibilities > > out there nowadays ... > > i've seen it recently on either freebsd or linux, > in the case of trying to remove or perhaps overwrite > binaries that were being executed at the time. overwrite, yeah. That EBUSY will definitely occur for overwrite in different ways on different unices. Now I see what you meant. On freebsd and Linux, exec happens via an mmap (more or less). Possibly the behavioural difference you saw between binary and normal file was due to how the kernels handle mmap for exec vs. file I/O, not due to it being a binary vs. normal file. ron