From owner-freebsd-hackers Sun Jun 9 07:41:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA10361 for hackers-outgoing; Sun, 9 Jun 1996 07:41:43 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA10336; Sun, 9 Jun 1996 07:41:38 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id aa23651; 9 Jun 96 14:41 GMT Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa28517; 9 Jun 96 14:08 +0100 Received: (from fhackers@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id KAA01634; Sun, 9 Jun 1996 10:59:25 GMT Date: Sun, 9 Jun 1996 10:59:25 GMT Message-Id: <199606091059.KAA01634@jraynard.demon.co.uk> From: James Raynard To: bde@zeta.org.au CC: hackers@freebsd.org, phk@freebsd.org In-reply-to: <199606090548.PAA26171@godzilla.zeta.org.au> (message from Bruce Evans on Sun, 9 Jun 1996 15:48:18 +1000) Subject: Re: bit 7 in filenames Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Bruce Evans 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