Date: Wed, 10 May 1995 12:39:28 +0200 From: Bernard.Steiner@Germany.EU.net To: terry@cs.weber.edu (Terry Lambert) Cc: freebsd-bugs@FreeBSD.org Subject: Re: strange symlinks Message-ID: <199505101040.MAA18416@qwerty.Germany.EU.net> In-Reply-To: Your message of Tue, 09 May 1995 16:14:48 MDT. <9505092214.AA19830@cs.weber.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> The next one may be a general 4.4 problem...
> assumption: /tmp/foo does not exist, /tmp/bar is a symlink to /tmp/foo.
> chdir("/tmp/bar") fails with ENOENT, but at the same time
> mkdir("/tmp/bar", 0x777) fails with EEXIST.
I think this is a generic result of the path component item evaluation
order. I guess the only thing to say is that "according to the code,
this is correct behaviour" 8-).
Yeah. There's more to this, actually. If you do an open(O_CREAT)
(on SunOS4.1.3; haven't got the FreeBSD box with me now) you get a normal open
file that the symlink points to. IN the light of the mkdir, this is a wee bit
inconsistent, isn't it ?
> Third, whatever happened to the fchdir() syscall that I vaguely remember
> having had in (at least) 386BSD0.1 ?
Sorry - please delete all my ranting on this one.
Bernard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505101040.MAA18416>