From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
Date: Sat, 03 Mar 2018 18:14:00 -0000 [thread overview]
Message-ID: <468c8201-f85c-d1ce-a50b-2b983a70edaf@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAKqBF1jHmZCo5a4hsZ4oHrEO8WODoeatO8m-xZaje5Um1X-jLg@mail.gmail.com>
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: 7233 Blocks: 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.000000000 +0000
> Modify: 2018-03-02 11:50:12.000000000 +0000
> Change: 2018-03-02 11:50:12.000000000 +0000
> Birth: 2018-03-02 09:26:44.060000000 +0000
>
> ~> dos2unix.exe /j/PStart.xml
> dos2unix: converting file /j/PStart.xml to Unix format...
>
> ~> stat /j/PSTART.XML
> File: /j/PSTART.XML
> Size: 6943 Blocks: 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.000000000 +0000
> Modify: 2018-03-03 08:27:16.000000000 +0000
> Change: 2018-03-03 08:27:16.000000000 +0000
> Birth: 2018-03-03 08:27:15.210000000 +0000
>
> 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
next prev parent reply other threads:[~2018-03-03 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 8:36 Fergus Daly
2018-03-03 18:14 ` Brian Inglis [this message]
2018-03-04 10:09 ` Corinna Vinschen
2018-03-04 16:14 ` Brian Inglis
2018-03-04 17:05 ` cyg Simple
2018-03-04 18:14 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 14:57 Fergus Daly
2018-03-06 17:58 ` Brian Inglis
2018-03-05 9:05 Fergus Daly
2018-03-05 16:44 ` Michel LaBarre
2018-03-05 16:46 ` Corinna Vinschen
2018-03-05 17:13 ` Michel LaBarre
2018-03-05 17:16 ` Corinna Vinschen
2018-03-05 18:04 ` Michel LaBarre
2018-03-05 21:00 ` Corinna Vinschen
2018-03-06 3:20 ` Michel LaBarre
2018-03-02 9:41 Fergus Daly
2018-03-02 16:55 ` Brian Inglis
2018-03-02 17:50 ` Andrey Repin
2018-03-02 9:22 Fergus Daly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=468c8201-f85c-d1ce-a50b-2b983a70edaf@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).