Message-ID:	<399A95F4.1A446F4F@softhome.net>
Date:	Wed, 16 Aug 2000 15:24:04 +0200
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.74 [en] (Win98; U)
X-Accept-Language:	lt,en
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
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> <1438-Wed16Aug2000155816+0300-eliz AT is DOT elta DOT co DOT il>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> 
> > 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:

If we are going to provide readlink() FSEXT hook, then this chapter goes to
thrash bin anyway.

Laurynas

- Raw text -