Date: Sun, 9 Jun 1996 10:59:25 GMT From: James Raynard <fhackers@jraynard.demon.co.uk> To: bde@zeta.org.au Cc: hackers@freebsd.org, phk@freebsd.org Subject: Re: bit 7 in filenames Message-ID: <199606091059.KAA01634@jraynard.demon.co.uk> In-Reply-To: <199606090548.PAA26171@godzilla.zeta.org.au> (message from Bruce Evans on Sun, 9 Jun 1996 15:48:18 %2B1000)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> Bruce Evans <bde@zeta.org.au> writes:
>
> > 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.
Do I detect another job to do as part of my libc cleanup? 8-)
> >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).
Will this still be true after the msdosfs re-write?
--
James Raynard, Edinburgh, Scotland | http://www.freebsd.org/~jraynard/
james@jraynard.demon.co.uk | jraynard@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606091059.KAA01634>