Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On 2018-03-06 07:01, Fergus Daly wrote: >>> I looked for recent similar issues and only found > https://superuser.com/questions/1297658/folder-names-become-uppercase-when-syncing-to-fat32-drive Have you checked that you get identical behaviour under cmd shell or PowerShell, and see the problem using dir? This would confirm that it is a file system problem and not the calls used. >>> 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. Settings/bottom of page/Make Windows better/Give us feedback > 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( -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
>> 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
RE: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
> -Original Message- > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On > Behalf Of Corinna Vinschen > Sent: March 5, 2018 2:55 PM > To: cygwin@cygwin.com > Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on > FAT32 > > On Mar 5 12:46, Michel LaBarre wrote: > > Sorry folks but I am going to top post for the sake of clarity. The > > original > msg is below for reference. > > > > Corinna, I ran the following and I attached the trace file: > > E:\junk>ls > Zot.txt > > E:\junk>ls > > Zot.txt > > E:\junk>strace -o d2u.trace dos2unix -n Zot.txt Zot.txt > > dos2unix: converting file Zot.txt to file Zot.txt in Unix format... > > E:\junk>ls > > ZOT.TXT d2u.trace > > [...] > > Thanks. The culprit is really most likely the system. Cygwin never > observes or uses an all-uppercase name while doing its thing. I agree it is likely the system but it is curious that the only program that readily displays the problem is dos2unix (and unix2dos and mac2unix and unix2mac - I tried them). 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. If RedHat has some dev contacts, you might have more luck highlighting the issue than riffraff like us. Fergus: Looking at the first trace file, the very last rename operation looks to be where the final filename is established. If you were to compile a short program doing exactly that call will little else, you might confirm a minimal reproduceable case. Here's one last variation: E:\junk>ls > Abc.txt12 E:\junk>dos2unix Abc.txt12 dos2unix: converting file Abc.txt12 to Unix format... E:\junk>ls Abc.txt12 The target name is not 8dot3 conforming and all case is preserved. Same with Abcdefghijkl.txt The target name seems to only fail when it looks to be 8dot3 conforming. /Michel > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Maintainer cygwin AT cygwin DOT com > Red Hat -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On Mar 5 12:46, Michel LaBarre wrote: > Sorry folks but I am going to top post for the sake of clarity. The original > msg is below for reference. > > Corinna, I ran the following and I attached the trace file: > E:\junk>ls > Zot.txt > E:\junk>ls > Zot.txt > E:\junk>strace -o d2u.trace dos2unix -n Zot.txt Zot.txt > dos2unix: converting file Zot.txt to file Zot.txt in Unix format... > E:\junk>ls > ZOT.TXT d2u.trace > [...] Thanks. The culprit is really most likely the system. Cygwin never observes or uses an all-uppercase name while doing its thing. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On Mar 5 12:05, Michel LaBarre wrote: > > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On > > Behalf Of Corinna Vinschen > > On Mar 5 11:42, Michel LaBarre wrote: > > > I have the same build 16299.248 and I get the same behaviour. > > > Perhaps consider: http://www.zoneutils.com/regtricks/filesystem.htm > > > for parameters to experiment with. You can use fsutil to control some of > > these to avoid direct registry modifications. > > > I expect it is more subtle otherwise the pervasive nature of the flags > > > would > > mean that any file creation would result in UC names, not just dos2unix. > > > i.e. ls > Foo.txt should produce FOO.TXT > > > > Maybne something with overwriting existung files? What if you call > > `ls > Foo.txt' twice in a row? > > > > Nope - that works ok. (BTW - you were fast on the reply!) > > I did try: > E:\>dos2unix -n Zot.txt Foo.txt > dos2unix: converting file Zot.txt to file Foo.txt in Unix format... > E:\>ls >Foo.txtZot.txt > > I thought using -n might suffice as a quick workaround for Fergus so I tried: > > E:\>dos2unix -n Zot.txt Zot.txt > dos2unix: converting file Zot.txt to file Zot.txt in Unix format... > E:\>ls >Foo.txt ZOT.TXT But `mv ZOT.TXT Zot.txt' works? Can you strace this like this after renaming the file back to Zot.txt $ strace -o d2u.trace dos2unix -n Zot.txt Zot.txt and send the d2u.trace file to this list? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
RE: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
> -Original Message- > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On > Behalf Of Corinna Vinschen > > On Mar 5 11:42, Michel LaBarre wrote: > > > > > Behalf Of Fergus Daly > > > Starting to look exactly like that. On Windows 7 there is no problem. > > > On earlier W10 machines in this office there is no problem. My machine > > > underwent a massive (time-consuming) update on or around 13-FEB to > > > Microsoft Windows Version 1709 Build 16299.248] > > > from the previous > > > Microsoft Windows Version 1703 Build 15063.936] > > > and the troubles began then: > > > > > > ~> touch TryThis.TxT > > > ~> ls T* > > > TryThis.TxT > > > ~> dos2unix TryThis.TxT > > > dos2unix: converting file TryThis.TxT to Unix format... > > > ~> ls T* > > > TRYTHIS.TXT > > > > > > This on a FAT32 stick. (Can anybody confirm this behaviour?) So I'm > > > guessing Windows has revised its default mount shortname syntax for > > > VFAT. Is there a way I can climb in and alter / override that, does > > > anybody know? > > > > I have the same build 16299.248 and I get the same behaviour. > > Perhaps consider: http://www.zoneutils.com/regtricks/filesystem.htm > > for parameters to experiment with. You can use fsutil to control some of > these to avoid direct registry modifications. > > I expect it is more subtle otherwise the pervasive nature of the flags would > mean that any file creation would result in UC names, not just dos2unix. > > i.e. ls > Foo.txt should produce FOO.TXT > > Maybne something with overwriting existung files? What if you call > `ls > Foo.txt' twice in a row? > Nope - that works ok. (BTW - you were fast on the reply!) I did try: E:\>dos2unix -n Zot.txt Foo.txt dos2unix: converting file Zot.txt to file Foo.txt in Unix format... E:\>ls Foo.txtZot.txt I thought using -n might suffice as a quick workaround for Fergus so I tried: E:\>dos2unix -n Zot.txt Zot.txt dos2unix: converting file Zot.txt to file Zot.txt in Unix format... E:\>ls Foo.txt ZOT.TXT Nuts! So the problem manifests if the input and output files are the same whether using -n or not. (Sorry Fergus - no workaround.) As an aside, I experimented with "ed" to change a file and re-write it presuming it might behave as dos2nix - nope - it preserved mixed case ok. Michel > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Maintainer cygwin AT cygwin DOT com > Red Hat -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On Mar 5 11:42, Michel LaBarre wrote: > > > > -Original Message- > > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On > > Behalf Of Fergus Daly > > Sent: March 5, 2018 4:06 AM > > To: The Cygwin Mailing List > > Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on > > FAT32 > > > > >> ..."or operation on FAT32 was changed by Windows updates." > > > > Starting to look exactly like that. On Windows 7 there is no problem. > > On earlier W10 machines in this office there is no problem. My machine > > underwent a massive (time-consuming) update on or around 13-FEB to > > Microsoft Windows Version 1709 Build 16299.248] > > from the previous > > Microsoft Windows Version 1703 Build 15063.936] > > and the troubles began then: > > > > ~> touch TryThis.TxT > > ~> ls T* > > TryThis.TxT > > ~> dos2unix TryThis.TxT > > dos2unix: converting file TryThis.TxT to Unix format... > > ~> ls T* > > TRYTHIS.TXT > > > > This on a FAT32 stick. (Can anybody confirm this behaviour?) So I'm > > guessing Windows has revised its default mount shortname syntax for > > VFAT. Is there a way I can climb in and alter / override that, does > > anybody know? > > I have the same build 16299.248 and I get the same behaviour. > Perhaps consider: http://www.zoneutils.com/regtricks/filesystem.htm > for parameters to experiment with. You can use fsutil to control some of > these to avoid direct registry modifications. > I expect it is more subtle otherwise the pervasive nature of the flags would > mean that any file creation would result in UC names, not just dos2unix. > i.e. ls > Foo.txt should produce FOO.TXT Maybne something with overwriting existung files? What if you call `ls > Foo.txt' twice in a row? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
RE: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
> -Original Message- > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On > Behalf Of Fergus Daly > Sent: March 5, 2018 4:06 AM > To: The Cygwin Mailing List > Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on > FAT32 > > >> ..."or operation on FAT32 was changed by Windows updates." > > Starting to look exactly like that. On Windows 7 there is no problem. > On earlier W10 machines in this office there is no problem. My machine > underwent a massive (time-consuming) update on or around 13-FEB to > Microsoft Windows Version 1709 Build 16299.248] > from the previous > Microsoft Windows Version 1703 Build 15063.936] > and the troubles began then: > > ~> touch TryThis.TxT > ~> ls T* > TryThis.TxT > ~> dos2unix TryThis.TxT > dos2unix: converting file TryThis.TxT to Unix format... > ~> ls T* > TRYTHIS.TXT > > This on a FAT32 stick. (Can anybody confirm this behaviour?) So I'm > guessing Windows has revised its default mount shortname syntax for > VFAT. Is there a way I can climb in and alter / override that, does > anybody know? I have the same build 16299.248 and I get the same behaviour. Perhaps consider: http://www.zoneutils.com/regtricks/filesystem.htm for parameters to experiment with. You can use fsutil to control some of these to avoid direct registry modifications. I expect it is more subtle otherwise the pervasive nature of the flags would mean that any file creation would result in UC names, not just dos2unix. i.e. ls > Foo.txt should produce FOO.TXT My dos2unix is version 7.3.5 Cygcheck -V is 2.9.0 > > 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 -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
>> ..."or operation on FAT32 was changed by Windows updates." Starting to look exactly like that. On Windows 7 there is no problem. On earlier W10 machines in this office there is no problem. My machine underwent a massive (time-consuming) update on or around 13-FEB to Microsoft Windows Version 1709 Build 16299.248] from the previous Microsoft Windows Version 1703 Build 15063.936] and the troubles began then: ~> touch TryThis.TxT ~> ls T* TryThis.TxT ~> dos2unix TryThis.TxT dos2unix: converting file TryThis.TxT to Unix format... ~> ls T* TRYTHIS.TXT This on a FAT32 stick. (Can anybody confirm this behaviour?) So I'm guessing Windows has revised its default mount shortname syntax for VFAT. Is there a way I can climb in and alter / override that, does anybody know? 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On 2018-03-04 10:05, cyg Simple wrote:
> On 3/4/2018 11:14 AM, Brian Inglis wrote:
>> On 2018-03-04 03:09, Corinna Vinschen wrote:
>>> On Mar 3 11:14, Brian Inglis wrote:
On 2018-03-03 01:36, Fergus Daly wrote:
>>> Run stat on original and converted files.
>
> OK. I get this:
>
> ~> stat /j/PStart.xml
> File: /j/PStart.xml
> Size: 7233Blocks: 8 IO Block: 65536 regular file
> Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1
> Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd)
> Access: 2018-03-03 00:00:00.0 +
> Modify: 2018-03-02 11:50:12.0 +
> Change: 2018-03-02 11:50:12.0 +
> Birth: 2018-03-02 09:26:44.06000 +
>
> ~> dos2unix.exe /j/PStart.xml
> dos2unix: converting file /j/PStart.xml to Unix format...
>
> ~> stat /j/PSTART.XML
> File: /j/PSTART.XML
> Size: 6943Blocks: 8 IO Block: 65536 regular file
> Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1
> Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd)
> Access: 2018-03-03 00:00:00.0 +
> Modify: 2018-03-03 08:27:16.0 +
> Change: 2018-03-03 08:27:16.0 +
> Birth: 2018-03-03 08:27:15.21000 +
>
> Does that help at all?
>
> It's not so much the behaviour on FAT32, which I could put up with as
> a filesystem pehenomenon if it had always been the case: but it's just
> started in the past few days. Can't think what has been updated that
> would cause this change. Previously sed and dos2unix which I use
> constantly (and others) did NOT change the case of the filename.
Should only be possible if Std C rename was changed in newlib/Cygwin1.dll
updates
>>>
>>> No changes there, certainly not renaming the file to all uppercase.
>>
>> Not suggesting any deliberate impact from newlib/Cygwin but any change could
>> result in different Windows calls in the emulation layer, or the cause could
>> be
>> as in the rest of the sentence trimmed:
>>
>> ..."or operation on FAT32 was changed by Windows updates."
>
> IIRC, the original FAT only allowed uppercase file names. Maybe some
> emulation switch is on as a result of such updates at the Windows level.
That's FAT12/16 (floppy/HD) - FAT32, exFAT support VFAT, and case and other
attributes should be retained on {Move,Replace}File{Ex,...}W, from MS docs.
The question may be what holds for ...A functions: those should be wrappers
calling the ...W functions, or the underlying functions.
Sometimes MS add new functions or change parameters you need to use to maintain
legacy behaviour after OS changes.
"Never attribute to malice that which is adequately explained by stupidity."
- Hanlon's Razor
"90% of everything is crap."
- Sturgeon's Law
Cygwin provides and supports the other 10% of Unix! ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On 3/4/2018 11:14 AM, Brian Inglis wrote: > On 2018-03-04 03:09, Corinna Vinschen wrote: >> On Mar 3 11:14, Brian Inglis wrote: >>> On 2018-03-03 01:36, Fergus Daly wrote: >> Run stat on original and converted files. OK. I get this: ~> stat /j/PStart.xml File: /j/PStart.xml Size: 7233Blocks: 8 IO Block: 65536 regular file Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) Access: 2018-03-03 00:00:00.0 + Modify: 2018-03-02 11:50:12.0 + Change: 2018-03-02 11:50:12.0 + Birth: 2018-03-02 09:26:44.06000 + ~> dos2unix.exe /j/PStart.xml dos2unix: converting file /j/PStart.xml to Unix format... ~> stat /j/PSTART.XML File: /j/PSTART.XML Size: 6943Blocks: 8 IO Block: 65536 regular file Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) Access: 2018-03-03 00:00:00.0 + Modify: 2018-03-03 08:27:16.0 + Change: 2018-03-03 08:27:16.0 + Birth: 2018-03-03 08:27:15.21000 + Does that help at all? It's not so much the behaviour on FAT32, which I could put up with as a filesystem pehenomenon if it had always been the case: but it's just started in the past few days. Can't think what has been updated that would cause this change. Previously sed and dos2unix which I use constantly (and others) did NOT change the case of the filename. >>> >>> Should only be possible if Std C rename was changed in newlib/Cygwin1.dll >>> updates >> >> No changes there, certainly not renaming the file to all uppercase. > > Not suggesting any deliberate impact from newlib/Cygwin but any change could > result in different Windows calls in the emulation layer, or the cause could > be > as in the rest of the sentence trimmed: > > ..."or operation on FAT32 was changed by Windows updates." > IIRC, the original FAT only allowed uppercase file names. Maybe some emulation switch is on as a result of such updates at the Windows level. -- cyg Simple -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On 2018-03-04 03:09, Corinna Vinschen wrote:
> On Mar 3 11:14, Brian Inglis wrote:
>> On 2018-03-03 01:36, Fergus Daly wrote:
> Run stat on original and converted files.
>>>
>>> OK. I get this:
>>>
>>> ~> stat /j/PStart.xml
>>> File: /j/PStart.xml
>>> Size: 7233Blocks: 8 IO Block: 65536 regular file
>>> Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1
>>> Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd)
>>> Access: 2018-03-03 00:00:00.0 +
>>> Modify: 2018-03-02 11:50:12.0 +
>>> Change: 2018-03-02 11:50:12.0 +
>>> Birth: 2018-03-02 09:26:44.06000 +
>>>
>>> ~> dos2unix.exe /j/PStart.xml
>>> dos2unix: converting file /j/PStart.xml to Unix format...
>>>
>>> ~> stat /j/PSTART.XML
>>> File: /j/PSTART.XML
>>> Size: 6943Blocks: 8 IO Block: 65536 regular file
>>> Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1
>>> Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd)
>>> Access: 2018-03-03 00:00:00.0 +
>>> Modify: 2018-03-03 08:27:16.0 +
>>> Change: 2018-03-03 08:27:16.0 +
>>> Birth: 2018-03-03 08:27:15.21000 +
>>>
>>> Does that help at all?
>>>
>>> It's not so much the behaviour on FAT32, which I could put up with as
>>> a filesystem pehenomenon if it had always been the case: but it's just
>>> started in the past few days. Can't think what has been updated that
>>> would cause this change. Previously sed and dos2unix which I use
>>> constantly (and others) did NOT change the case of the filename.
>>
>> Should only be possible if Std C rename was changed in newlib/Cygwin1.dll
>> updates
>
> No changes there, certainly not renaming the file to all uppercase.
Not suggesting any deliberate impact from newlib/Cygwin but any change could
result in different Windows calls in the emulation layer, or the cause could be
as in the rest of the sentence trimmed:
..."or operation on FAT32 was changed by Windows updates."
which could have affected any file naming e.g.
\{Global??}\{[?.]}\{GLOBALROOT\}... paths, encoding, or
{Move,Replace}File{Ex,Transacted,WithProgress}{A,W} functions, as we already
know there have been some changes in the open access rights and sharing modes
used on W10, which should not but could possibly affect name preservation
depending on the Windows path namespaces.
[From personal experience, I know they have messed up, and fixed those problems
in subsequent updates, with systems running old and crufty (like me and mine)
AMD CPUs, HP monitors, and HP printers: summer patches from vendors' summer
students have long been questionable, and advisable to wait until autumn patches
for patches series appear.]
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On Mar 3 11:14, Brian Inglis wrote: > On 2018-03-03 01:36, Fergus Daly wrote: > >>> Run stat on original and converted files. > > > > OK. I get this: > > > > ~> stat /j/PStart.xml > > File: /j/PStart.xml > > Size: 7233Blocks: 8 IO Block: 65536 regular file > > Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 > > Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) > > Access: 2018-03-03 00:00:00.0 + > > Modify: 2018-03-02 11:50:12.0 + > > Change: 2018-03-02 11:50:12.0 + > > Birth: 2018-03-02 09:26:44.06000 + > > > > ~> dos2unix.exe /j/PStart.xml > > dos2unix: converting file /j/PStart.xml to Unix format... > > > > ~> stat /j/PSTART.XML > > File: /j/PSTART.XML > > Size: 6943Blocks: 8 IO Block: 65536 regular file > > Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 > > Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) > > Access: 2018-03-03 00:00:00.0 + > > Modify: 2018-03-03 08:27:16.0 + > > Change: 2018-03-03 08:27:16.0 + > > Birth: 2018-03-03 08:27:15.21000 + > > > > Does that help at all? > > > > It's not so much the behaviour on FAT32, which I could put up with as > > a filesystem pehenomenon if it had always been the case: but it's just > > started in the past few days. Can't think what has been updated that > > would cause this change. Previously sed and dos2unix which I use > > constantly (and others) did NOT change the case of the filename. > > Should only be possible if Std C rename was changed in newlib/Cygwin1.dll > updates No changes there, certainly not renaming the file to all uppercase. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On 2018-03-03 01:36, Fergus Daly wrote: >>> Run stat on original and converted files. > > OK. I get this: > > ~> stat /j/PStart.xml > File: /j/PStart.xml > Size: 7233Blocks: 8 IO Block: 65536 regular file > Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 > Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) > Access: 2018-03-03 00:00:00.0 + > Modify: 2018-03-02 11:50:12.0 + > Change: 2018-03-02 11:50:12.0 + > Birth: 2018-03-02 09:26:44.06000 + > > ~> dos2unix.exe /j/PStart.xml > dos2unix: converting file /j/PStart.xml to Unix format... > > ~> stat /j/PSTART.XML > File: /j/PSTART.XML > Size: 6943Blocks: 8 IO Block: 65536 regular file > Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 > Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) > Access: 2018-03-03 00:00:00.0 + > Modify: 2018-03-03 08:27:16.0 + > Change: 2018-03-03 08:27:16.0 + > Birth: 2018-03-03 08:27:15.21000 + > > Does that help at all? > > It's not so much the behaviour on FAT32, which I could put up with as > a filesystem pehenomenon if it had always been the case: but it's just > started in the past few days. Can't think what has been updated that > would cause this change. Previously sed and dos2unix which I use > constantly (and others) did NOT change the case of the filename. Should only be possible if Std C rename was changed in newlib/Cygwin1.dll updates or operation on FAT32 was changed by Windows updates. Looks like VFAT entries are no longer being created for the long file name as it has a short name. Test what happens if you use a mixed long file name e.g. Mumblety-Peg.html? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
>> Run stat on original and converted files. OK. I get this: ~> stat /j/PStart.xml File: /j/PStart.xml Size: 7233Blocks: 8 IO Block: 65536 regular file Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) Access: 2018-03-03 00:00:00.0 + Modify: 2018-03-02 11:50:12.0 + Change: 2018-03-02 11:50:12.0 + Birth: 2018-03-02 09:26:44.06000 + ~> dos2unix.exe /j/PStart.xml dos2unix: converting file /j/PStart.xml to Unix format... ~> stat /j/PSTART.XML File: /j/PSTART.XML Size: 6943Blocks: 8 IO Block: 65536 regular file Device: a6418e7fh/2789314175d Inode: 7206475022584976007 Links: 1 Access: (0644/-rw-r--r--) Uid: (197609/ fergusd) Gid: (197609/ fergusd) Access: 2018-03-03 00:00:00.0 + Modify: 2018-03-03 08:27:16.0 + Change: 2018-03-03 08:27:16.0 + Birth: 2018-03-03 08:27:15.21000 + Does that help at all? It's not so much the behaviour on FAT32, which I could put up with as a filesystem pehenomenon if it had always been the case: but it's just started in the past few days. Can't think what has been updated that would cause this change. Previously sed and dos2unix which I use constantly (and others) did NOT change the case of the filename. 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
Greetings, Brian Inglis! > Does FAT support ACLs? No. -- With best regards, Andrey Repin Friday, March 2, 2018 20:46:37 Sorry for my terrible english... -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
On 2018-03-02 02:41, Fergus Daly wrote: > .. AND dos2unix: > ~> ls -al /j/P* > -rw-r--r-- 1 dell ferg 6767 Mar 2 09:15 /j/PStart.xml > ~> dos2unix /j/PStart.xml > dos2unix: converting file /j/PStart.xml to Unix format... > ~> ls -al /j/P* > -rw-r--r-- 1 dell ferg 6767 Mar 2 09:16 /j/PSTART.XML > So something a bit major seems to be going on .. .. Not writing VFAT directory entries, or with case preserving names? Run stat on original and converted files. Does FAT support ACLs? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
.. AND dos2unix: ~> ls -al /j/P* -rw-r--r-- 1 dell ferg 6767 Mar 2 09:15 /j/PStart.xml ~> dos2unix /j/PStart.xml dos2unix: converting file /j/PStart.xml to Unix format... ~> ls -al /j/P* -rw-r--r-- 1 dell ferg 6767 Mar 2 09:16 /j/PSTART.XML So something a bit major seems to be going on .. .. 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
