From owner-freebsd-current Mon Jun 18 23:12:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from glatton.cnchost.com (glatton.cnchost.com [207.155.248.47]) by hub.freebsd.org (Postfix) with ESMTP id 62F9337B403 for ; Mon, 18 Jun 2001 23:12:37 -0700 (PDT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by glatton.cnchost.com id CAA16188; Tue, 19 Jun 2001 02:12:34 -0400 (EDT) [ConcentricHost SMTP Relay 1.13] Message-ID: <200106190612.CAA16188@glatton.cnchost.com> To: Bruce Evans Cc: current@FreeBSD.ORG, Matt Dillon Subject: Re: Ok, try this patch. (was Re: symlink(2) [Was: Re: tcsh.cat]) In-reply-to: Your message of "Tue, 19 Jun 2001 15:56:01 +1000." Date: Mon, 18 Jun 2001 23:12:34 -0700 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > So it seems to me the _use_ of a "" target symlink > > (in all but the final path component position) is exactly > > equivalent to the use of a "/" target symlink. When used in > > the final path component position, you get either the symlink > > or ENOENT. The POSIX excerpt Garrett quoted seems to match > > this. > > No, because the relevant slash is in the pathname resulting from > simple replacement of the full path prefix (/) > with the symlink's contents. Quoting Garrett's quote: IMHO the key point is the *resulting* remaining pathname after substitution. Normally one would simply prepend the contents before the , see if the resulting pathname starts with a '/', if so start the search at root else start the search at the parent of symlink. In any case any leading slashes are removed. In other words the bits are not kept separately from bits. This is a simpler implementation and seems to match what posix says. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message