DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=ijyLtwW6QYiSiOU5uZGJ+v8yhxJLS
	gxSJ19ckUSQ2IcO+AGamCOPHN4ziNCufHxcEXzRdfUsiLS2HixtPZ6XKXPbzd5dP
	hkiAcUgUSNH75tPx989Ke98IS4m8myuaa9UaWUrjraYWfErtgoGerEfbDbZnZXUd
	fyNGesqHJrVw08=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Fergus Daly <ugly DOT leper AT gmail DOT com>
Date: Tue, 6 Mar 2018 14:01:43 +0000
Message-ID: <CAKqBF1i+bdudLM7rCX1N-TPrmOPhOwY8NPB6ox1tJEXzZ35YuA@mail.gmail.com>
Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="UTF-8"

>> I looked for recent similar issues and only found
https://superuser.com/questions/1297658/folder-names-become-uppercase-when-syncing-to-fat32-drive

>> So if other users of this Win10 build start tripping on this same problem and reporting it, it may get looked at by MS.

The site you mention also asked about variations in hardware or
formatting mechanism. I find the identical behaviour in USB drives
(local) and USB sticks (removable). In the past I have used Hitachi
Microdrive to render Removable sticks Local, but can't find a version
of this driver upgrade for 64-bit. (Not one that works, anyway.
Several that don't.) Also identical behaviours whether the filesystem
is formatted FAT32 in Windows or formatted FAT32 in Linux.

So summarising:

SOME (but not ALL) file transactions on FAT32 result in

"Mixed case but no spaces 8.3" -> "ALL UPPER CASE 8.3"

Examples are sed and dos2unix (and family); but not nano, or joe. I
can't think of anything that I could reasonably test on a folder
rather than a file to see the effect on foldername.

Goodness knows how to upstream anything to MS.

Finally, there was another Windows update yesterday, 05-MAR-2018: to
version 1709 OS build 16299.251. Hopes of a return to correct
behaviours were immediately dashed. :o(

Fergus

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple