From: "Michel LaBarre" <michel.labarre@rogers.com>
To: "'Fergus Daly'" <ugly.leper@gmail.com>,
"'The Cygwin Mailing List'" <cygwin@cygwin.com>
Subject: RE: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
Date: Mon, 05 Mar 2018 16:44:00 -0000 [thread overview]
Message-ID: <000a01d3b4a0$f54ede30$dfec9a90$@rogers.com> (raw)
In-Reply-To: <CAKqBF1jHvNbra2a=k12nAwDE2_0W14iG1v=KhuACzPmJmicfYA@mail.gmail.com>
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@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
next prev parent reply other threads:[~2018-03-05 16:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 9:05 Fergus Daly
2018-03-05 16:44 ` Michel LaBarre [this message]
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
-- 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-03 8:36 Fergus Daly
2018-03-03 18:14 ` Brian Inglis
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
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='000a01d3b4a0$f54ede30$dfec9a90$@rogers.com' \
--to=michel.labarre@rogers.com \
--cc=cygwin@cygwin.com \
--cc=ugly.leper@gmail.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).