From owner-freebsd-current Fri Jun 15 6: 0: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E213D37B406 for ; Fri, 15 Jun 2001 06:00:03 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA24483; Fri, 15 Jun 2001 22:59:42 +1000 Date: Fri, 15 Jun 2001 22:57:56 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Andrey A. Chernov" Cc: Adrian Browne , freebsd-current@FreeBSD.ORG Subject: Re: tcsh.cat In-Reply-To: <20010615160248.A16012@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Fri, 15 Jun 2001, Andrey A. Chernov wrote: > On Fri, Jun 15, 2001 at 13:15:04 +1000, Bruce Evans wrote: > > > Related bugs: > > - symlink(2) is happy to create a symlink to the empty pathname although > > empty pathnames are invalid. > > Maybe we need to fix symlink(2) then ? Maybe, but this doesn't seem to be permitted by POSIX.1-200x: P> int symlink(const char *path1, const char *path2); P> ... P> The string pointed to by path1 shall be treated only as a character P> string and shall not be validated as a pathname. symlink.2 is fuzzier and can be read as reqiring that the first arg is a (valid) "path name". B> int B> symlink(const char *name1, const char *name2); B> ... B> A symbolic link name2 is created to name1 (name2 is the name of the file B> created, name1 is the string used in creating the symbolic link). Either B> name may be an arbitrary path name; the files need not be on the same B> file system. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message