IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
sftp message lost in the spam filter..
This got shuffled aside because of a malformed "To:" line..
sorry for the delay in forwarding this to the right place..
- Bill
------- Forwarded Message
Message-ID: <63D30D6E10CFD11190A90000F805FE86051AC213%lespaul.process.com@localhost>
From: Richard Whalen <Whalenr%process.com@localhost>
To:
Cc: ietf-ssh%NetBSD.org@localhost
Subject: RE: Case sensitivity on sftp servers
Date: Mon, 8 Sep 2003 08:36:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
charset="iso-8859-1"
> -----Original Message-----
> From: Dan O'Reilly [mailto:dano%process.com@localhost]
> Sent: Sunday, September 07, 2003 10:43 PM
> To: Martin Pool
> Cc: ietf-ssh%NetBSD.org@localhost
> Subject: Re: Case sensitivity on sftp servers
>
>
> At 08:20 PM 9/7/2003, Martin Pool wrote:
> >So with case sensitivity on
> >
> > OPEN("README", WRITE|CREAT|EXCL|CASE_INSENSITIVE)
> >
> >in a directory containing "readme" ought to fail with
> >FILE_ALREADY_EXISTS even on a case-sensitive filesystem, and
> >
> > OPEN("README", READ|CASE_SENSITIVE)
> >
> >in a directory containing "readme" ought to fail with NO_SUCH_FILE
> >even on a case-insensitive filesystem?
>
> No, it wouldn't necessarily do so on VMS, which supports
> multiple versions
> of files.
What Dan should have said was that it would not fail on VMS because on VMS
ODS-2 volumes UPPERCASE is used to store filenames and they are
case-insensitive, so "README", "readme", "ReadMe" (and lots of other
variants) will all open the same file.
VMS ODS-5 volumes are CASE_PRESERVITIVE, but not CASE_SENSITIVE. On VMS,
it's the user's (process) decision as to whether or not files are treated in
a case sensitive manner.
- ----------------------
Richard Whalen
Process Software
------- End of Forwarded Message
Home |
Main Index |
Thread Index |
Old Index