Date: Mon, 28 Aug 2000 17:57:02 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: Patch: symlinks in mkstemp()
In-Reply-To: <39AA6D73.40E10BF2@softhome.net>
Message-ID: <Pine.SUN.3.91.1000828175259.17210E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 28 Aug 2000, Laurynas Biveinis wrote:

> This is the last missing piece in symlink puzzle, as pointed
> out by Eli. I'll submit yet another one patch which makes 
> open() to resolve leading dirs even with O_NOLINK flag, but
> is there anything else skipped?

When I wrote my message with the list of functions I thought needed to 
support symlinks in leading directories, I scanned the contents of 
djlsr203.zip looking for such functions.  But it would be nice if someone 
else's eyes could revisit the list of file-oriented functions and verify 
that nothing is missing.

The principle is that every function that is available on Unix should 
support symlinks.  Functions that are specific to DOS/Windows or to DJGPP 
do not need to support symlinks, unless we have good reasons to add that 
(e.g., because many Unix compatibility functions call that non-Unix 
function).

> Tested, works[*].

Looks okay.