Date: Tue, 2 Jul 1996 18:03:51 -0700 (PDT) From: Mike Pritchard <mpp> To: bde@zeta.org.au (Bruce Evans) Cc: hackers@FreeBSD.org, phk@FreeBSD.org Subject: Re: bit 7 in filenames Message-ID: <199607030103.SAA18655@freefall.freebsd.org> In-Reply-To: <199606090548.PAA26171@godzilla.zeta.org.au> from "Bruce Evans" at Jun 9, 96 03:48:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
(I know this is old, but I'm just now getting caught up on
some very old e-mail that I wanted to respond to).
I think that lite2 corrects some of this anachronisms.
It also fixes some of the hardcoded constants in
some of the man pages. E.g. instead of using
"1024", it will specify "MAXPATHLEN".
Bruce Evans wrote:
>
> > 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
>
--
Mike Pritchard
mpp@FreeBSD.org
"Go that way. Really fast. If something gets in your way, turn"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607030103.SAA18655>