Article View: mod.std.unix
Article #292Case sensitive file names
From: Moderator, John Quarterman
Date: Thu, 09 Oct 1986 00:28
Date: Thu, 09 Oct 1986 00:28
20 lines
1476 bytes
1476 bytes
From: seismo!hpscda!hpdsd!hpda!hpisoa1!davel (Dave Lennert) Date: Mon, 6 Oct 86 15:24:20 pdt Perhaps a good approach might be to require POSIX applications to specify filenames to the system as all lowercase in order to be truly portable. As long as the filenames don't contain *mixed* case then case shifting to all lower or all uppper (or leaving case insensitive) on the part of the system won't result in name collisions. A variant on this is to require all hardcoded filenames in applications to be lowercase, but filenames supplied by a user could be passed to the system unshifted by the application. The user should know the case limitations of the underlying system. However, my preference is to have the POSIX interface support cases sensitive filenames. I agree with others that this will not be hard to implement given some of the other things that will have to be provided. Volume-Number: Volume 7, Number 39
Technical Details
Message-ID:
<5961@ut-sally.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!ut-sally!std-unixShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!ut-sally!std-unix From: std-unix@ut-sally.UUCP (Moderator, John Quarterman) Newsgroups: mod.std.unix Subject: Case sensitive file names Message-ID: <5961@ut-sally.UUCP> Date: Wed, 8-Oct-86 20:28:55 EDT Article-I.D.: ut-sally.5961 Posted: Wed Oct 8 20:28:55 1986 Date-Received: Thu, 9-Oct-86 03:46:47 EDT Organization: IEEE P1003 Portable Operating System for Computer Environments Committee Lines: 20 Approved: jsq@sally.utexas.edu