From owner-freebsd-hackers  Sat Jun  8 22:51:40 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA23512
          for hackers-outgoing; Sat, 8 Jun 1996 22:51:40 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA23489;
          Sat, 8 Jun 1996 22:51:29 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA26171; Sun, 9 Jun 1996 15:48:18 +1000
Date: Sun, 9 Jun 1996 15:48:18 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199606090548.PAA26171@godzilla.zeta.org.au>
To: hackers@freebsd.org, phk@freebsd.org
Subject: Re: bit 7 in filenames
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>     The symbolic link succeeds unless:

>     [ENOTDIR]
>	       A component of the name2 prefix is not a directory.

>     [EINVAL]  Either name1 or name2 contains a character with the high-order
>	       bit set.

>HUH ????

This anachronism is in most of the man pages for system calls that involve
path names.

>Actually there should be an error return, if I try to make a filename
>that is illegal for the filesystem.

>For instance
>	create("/msdosfs/foo:bar")
>is an invalid name...

It's not invalid for msdosfs :-). :-(.  Neither is creat("/msdosfs/a2345678:
this is a very long not to mention invalid msdos path.name", 0666).
<sys/unistd.h> falsely advertises that _POSIX_NO_TRUNC is 1 (no-trunc for
_all_ supported file systems) and man pages misspell
pathconf("/mountpoint", _PC_NAME_MAX) as 255.

Bruce