Date: Wed, 16 Aug 2000 15:58:17 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: lauras AT softhome DOT net
Message-Id: <1438-Wed16Aug2000155816+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC: djgpp-workers AT delorie DOT com
In-reply-to: <399A8760.7F5943F3@softhome.net> (message from Laurynas Biveinis
	on Wed, 16 Aug 2000 14:21:52 +0200)
Subject: Re: Patch: open() adjustment for symlinks
References: <39998D7D DOT 70F85B9E AT softhome DOT net> <5137-Tue15Aug2000223737+0300-eliz AT is DOT elta DOT co DOT il> <3999A16F DOT F8809412 AT softhome DOT net> <3099-Wed16Aug2000002312+0300-eliz AT is DOT elta DOT co DOT il> <399A6110 DOT CA193440 AT softhome DOT net> <7263-Wed16Aug2000150127+0300-eliz AT is DOT elta DOT co DOT il> <399A8760 DOT 7F5943F3 AT softhome DOT net>
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

> Date: Wed, 16 Aug 2000 14:21:52 +0200
> From: Laurynas Biveinis <lauras AT softhome DOT net>
>  
> +Note that @code{__solve_symlinks} does not contain FSEXT handler, so
> +an extension cannot intercept symlink resolution directly.  However, 
> +@code{__solve_symlinks} eventually calls @code{_open} and @code{_read},
> +so if you provide open and read handlers, your extension should work OK
> +with symlinks too.

Two comments:

  - FSEXT should be in @code{}, and with a cross-reference to the node
    which explains file-system extensions;

  - I suggest to describe the format of the symlink, in case some
    FSEXT indeed would want to simulate them.