Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3E7992F3.B4381333@phekda.freeserve.co.uk>
Date:	Thu, 20 Mar 2003 10:07:47 +0000
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: fchdir, revision 2 [PATCH]
References:	<E18vcu4-0000a1-00 AT phekda DOT freeserve DOT co DOT uk> <7458-Wed19Mar2003174724+0200-eliz AT elta DOT co DOT il> <3E78AC79 DOT D615F93B AT phekda DOT freeserve DOT co DOT uk> <7458-Wed19Mar2003223447+0200-eliz AT elta DOT co DOT il> <3E78DB55 DOT 6A8E9C59 AT phekda DOT freeserve DOT co DOT uk> <2593-Thu20Mar2003061916+0200-eliz AT elta DOT co DOT il>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> 
> > Date: Wed, 19 Mar 2003 21:04:21 +0000
> > From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
> >
> > According to POSIX: You can't get a file descriptor for a symlink using
> > open(). For a symlink, open() should follow the symlink.
> >
> > We have the additional options:
> >
> > * O_NOFOLLOW, which causes open() to fail, if the file is a symlink.
> > * O_NOLINK, which causes open() to actually open the symlink as a normal
> >   file.
> >
> > If you've used O_NOLINK, I think it's reasonable to return info about the
> > symlink.
> 
> Okay, thanks.  So this logic should be inside `open', and `fstat'
> doesn't have to care about the issue.
[snip]

Yes, the logic is inside 'open'.

I'll commit the patch next Wednesday, if there's no further comment.

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -