From owner-freebsd-hackers  Sun Jun  9 12:59:14 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA14454
          for hackers-outgoing; Sun, 9 Jun 1996 12:59:14 -0700 (PDT)
Received: from eac.iafrica.com (slipper101139.iafrica.com [196.7.101.139])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA14424;
          Sun, 9 Jun 1996 12:58:54 -0700 (PDT)
Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id VAA00271; Sun, 9 Jun 1996 21:49:49 +0200
From: Robert Nordier <rnordier@iafrica.com>
Message-Id: <199606091949.VAA00271@eac.iafrica.com>
Subject: Re: bit 7 in filenames
To: fhackers@jraynard.demon.co.uk (James Raynard)
Date: Sun, 9 Jun 1996 21:49:48 +0200 (SAT)
Cc: bde@zeta.org.au, hackers@freebsd.org, phk@freebsd.org
In-Reply-To: <199606091059.KAA01634@jraynard.demon.co.uk> from "James Raynard" at Jun 9, 96 10:59:25 am
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

James Raynard wrote:

[...]
> > >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?

The vfatfs (== rewritten msdosfs) will not actually create files
containing illegal DOS filename characters.

Currently, however, it offers a `translate' option which does a
semi-intelligent mapping between characters valid on BSD and DOS.

(Invalid DOS filename characters are those below 0x20, as well as
the following sixteen:

     " * + , . / : ; < = > ? [ \ ] |

All other characters including 0x20 and characters >= 0x80 are
legal.)

With the translate option enabled, Bruce's example would be
acceptable, would be mapped to (say)

     /msdosfs/a2345678 this is a very long not to mention invalid
     msdos path.name

(which DOS itself would accept) and would result in the file

     A2345678.NAM

on a FAT filesystem.

--
Robert Nordier