On Aug 4 13:08, Linda Walsh wrote:
> Corinna Vinschen wrote:
> >On Aug 3 19:42, Linda Walsh wrote:
> >>Shaddy Baddah wrote:
> >>>This is the output for L: drive, which is not a physical but logical
> >>>volume formatted EXFAT. Hopefully it doesn't alter the
> >>>characteristics/attributes. With a
Corinna Vinschen wrote:
On Aug 3 19:42, Linda Walsh wrote:
Shaddy Baddah wrote:
This is the output for L: drive, which is not a physical but logical
volume formatted EXFAT. Hopefully it doesn't alter the
characteristics/attributes. With a bit of extra effort, I could try with
a physical device
On Aug 3 19:42, Linda Walsh wrote:
> Shaddy Baddah wrote:
> >
> >This is the output for L: drive, which is not a physical but logical
> >volume formatted EXFAT. Hopefully it doesn't alter the
> >characteristics/attributes. With a bit of extra effort, I could try with
> >a physical device (format a
Shaddy Baddah wrote:
To be honest, my bug bear with NTFS has been the file/folder ownership.
But I think noacl's is probably the best compromise for general NTFS
ACL issues.
You realize you can change the ownership of files in cygwin, no?
chmod . -R .
in your home directory, followed by
chmo
Shaddy Baddah wrote:
This is the output for L: drive, which is not a physical but logical
volume formatted EXFAT. Hopefully it doesn't alter the
characteristics/attributes. With a bit of extra effort, I could try with
a physical device (format a spare USB stick EXFAT through Windows):
$ /usr/li
Hi,
On 02 Aug 2013 20:29+1000, Corinna Vinschen wrote:
On Aug 2 19:05, Shaddy Baddah wrote:
Hi,
On 02 Aug 2013 18:31+1000, Corinna Vinschen wrote:
Correction, not only NTFS. Here's the source code comment:
Sorry, yes I forgot that it was coded to let Windows make the decision.
Unfortuna
On Aug 2 19:05, Shaddy Baddah wrote:
> Hi,
>
> On 02 Aug 2013 18:31+1000, Corinna Vinschen wrote:
> >Correction, not only NTFS. Here's the source code comment:
>
> Sorry, yes I forgot that it was coded to let Windows make the decision.
>
> >>Unfortunately, in providing EXFAT, Microsoft has not
Hi,
On 02 Aug 2013 18:31+1000, Corinna Vinschen wrote:
Correction, not only NTFS. Here's the source code comment:
Sorry, yes I forgot that it was coded to let Windows make the decision.
Unfortunately, in providing EXFAT, Microsoft has not seen fit to carry
over the same handling in the kern
On Aug 2 16:50, Shaddy Baddah wrote:
> Hi,
>
> As per:
>
> http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
>
> Cygwin act on filenames on NTFS in with case preservation/sensitivity.
Correction, not only NTFS. Here's the source code comment:
/* Case sensitivi
Hi,
As per:
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
Cygwin act on filenames on NTFS in with case preservation/sensitivity.
As this was a feature configured in the Windows kernel, the pre-existing
limitation whereby the same case sensitivity was not avail
10 matches
Mail list logo