Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: Case sensitive file names
Message-ID: <6304@ut-sally.UUCP>
Date: Sat, 8-Nov-86 18:16:52 EST
Article-I.D.: ut-sally.6304
Posted: Sat Nov  8 18:16:52 1986
Date-Received: Sun, 9-Nov-86 04:18:43 EST
References: <6226@ut-sally.UUCP>
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 27
Approved: jsq@sally.utexas.edu

From: seismo!enea!chalmers.UUCP!jacob (Jacob Hallen)
Date: Fri, 7 Nov 86 23:35:50 -0100
Organization: Dept. of CS, Chalmers, Sweden

>We seem to have three proposals:
>
>CS: Case sensitive file systems.  This is what all major Unix variants
>    (V6, V7, SysIII, SysV, 2BSD, and 4BSD) now support.
>
>CC: Case coercive file systems (file names forced to all upper or all
>    lower case).
>
>CR: Case retaining but otherwise insensitive file systems (new names
>    are created according to the given case; matches are not case
>    sensitive).
>

There is a serious flaw in the CR case! You lose orthogonality in
the interpretation of commands since creations, moves, copies and
some other file operations will interpret arguments literally while
other commands will have their arguments interpreted in the flexible way.
A move by the way is a good example since one argument will be treated
in one way and the other in the other way.

Jacob Hallen

Volume-Number: Volume 8, Number 49