Re: [PATCH] Do _not_ call unlink on a directory

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Jul 16, 2007, 21:44 UTC
Message-ID: <alpine.LFD.0.999.0707161442410.20061@woody.linux-foundation.org>
In-Reply-To: <469BE1D4.1070408@slamb.org>

On Mon, 16 Jul 2007, Scott Lamb wrote:

> 
> But Solaris remove() is broken, too, so it's a moot point.

In fact, with the Solaris behaviour for unlink(), you *cannot* have a non-broken "remove()".

So the right fix is always to fix "unlink()" instead.

There really aren't any downsides (since no program can rely on it 
_anyway_, unless we're talking about some magic "early bootup" time 
scripts that depend on only running as root, and only ever running on UFS 
- but those kinds of scripts could be trivially fixed and are obviously 
under Sun control anyway)

			Linus