In some email I received from Greg A. Woods, sie wrote:
> [ On Wednesday, June 12, 2002 at 21:46:05 (-0400), kpneal@pobox.com wrote: ]
> > Subject: Re:  FFS reliability problems
> >
> > Who wants to try to explain to users why sometimes they can rm a file
> > and sometimes they can't? 
> 
> What's to explain?  If the file is not open then the file is unlinked
> and its storage free for reuse, but if the file is open then the kernel
> returns EBUSY (or some new code like EOPEN).  This is not a new or
> radically different concept -- it's all been done before and anyone with
> any length of experience should already be very familiar with the idea.

Why are you perusing this Greg ?  Are you insane or something else ?

I just cannot believe what you're writing here - give up, will you ?

Nobody is going to break NetBSD just for you - go and create WoodsBSD,
will you ?

Darren