Eric Blake <[EMAIL PROTECTED]> writes:
> Lacking an efficient standardized API, checks for case-insensitivity are only
> needed when stricmp() succeeds when strcmp() fails (actually, I'm not sure
> whether choice of locale can affect case-insensitive equality of filenames?).
>
I would figure
Jonathan Lennox cs.columbia.edu> writes:
> On Cygwin using non-managed mounts (and presumably other operating systems
> when using a case-insensitive file system), it's not possible to use
> Coreutils mv to change the case of a filename; mv reports that they are the
> same file.
There is another
Jonathan Lennox scripsit:
> No, on Cygwin rename(2) will change file case:
Ah, sorry. I had mixed up what rename(2) does with what mv does.
--
First known example of political correctness: John Cowan
After Nurhachi had united all the other http://www.ccil.org/~cowan
Jurchen tribes un
On Thursday, August 16 2007, "John Cowan" wrote to "Eric Blake, John Cowan,
Jonathan Lennox, bug-coreutils@gnu.org" saying:
> Eric Blake scripsit:
>
> > You missed my earlier remark - since POSIX requires case sensitivity,
> > a case-insensitive file system is not specified by POSIX, therefore,
Eric Blake scripsit:
> You missed my earlier remark - since POSIX requires case sensitivity,
> a case-insensitive file system is not specified by POSIX, therefore,
> a platform may do whatever it likes with rename(2), including change
> the case (rather than be a no-op).
Well and good. In fact,
Eric Blake wrote:
[snip] Mac HFS is the other biggest case-preserving
case-insensitive system out there; can anyone comment on
whether rename(2) is a no-op or changes case when given two
case-wise distinct spellings of the same file?
Adding to what Jonathan already posted...
$ df -T .
Filesyst
>
> FAT is always upper case and the driver forces it to
> lower case. VFAT ignores attempts to change case
> with rename(), in conformity to Posix.
You missed my earlier remark - since POSIX requires
case sensitivity, a case-insensitive file system is not
specified by POSIX, therefore, a platfo
On Wednesday, August 15 2007, "Eric Blake" wrote to "Jonathan Lennox,
bug-coreutils@gnu.org" saying:
> > (I reported this issue on the bug tracker on Savannah, but it looks like
> > sending bug reports to this mailing list is preferred, so I'm repeating it
> > here.)
>
> The bug-tracker forwards
Eric Blake scripsit:
> Consider - should
> rename("Foo", "foo") be a no-op when stat("Foo") and stat("foo")
> resolve to the same file? Reading just the POSIX rename(2)
> requirements seems to say yes (it requires rename to be a no-op
> when both names resolve to the same inode, ie. no case chang
> (I reported this issue on the bug tracker on Savannah, but it looks like
> sending bug reports to this mailing list is preferred, so I'm repeating it
> here.)
The bug-tracker forwards all edits to this list, so you just repeated
yourself.
>
> On Cygwin using non-managed mounts (and presumably
(I reported this issue on the bug tracker on Savannah, but it looks like
sending bug reports to this mailing list is preferred, so I'm repeating it
here.)
On Cygwin using non-managed mounts (and presumably other operating systems
when using a case-insensitive file system), it's not possible to use
11 matches
Mail list logo
