News for hackers. Stuff that matters.
Re:Apple File System by imglorp on Monday June 13, 2016 @04:39PM (#11897426)
I think you have it backwards. If you try to expand an archive with FOO.TXT and foo.txt, what should happen if you're writing to a case insensitive file system?

    $ touch HI
    $ touch hi
    $ ls
    HI
So that's disturbing. Another problem is every software you can think of will be comparing two files case insensitively. Almost weekly I get burned by this.

    $ touch HI
    $ test -f hi && echo ok
    ok
Re:Apple File System by bjt on Monday June 13, 2016 @05:57PM (#11898052)
That's not convincing me that I have it backwards. I was responding to this point in the parent comment:

> many case insensitive hard drives would be copied into new machines and there would be millions of conflicts

I still don't see where you get a conflict copying the contents of a case-insensitive file system to a case-sensitive one.

Re:Apple File System by cynix on Monday June 13, 2016 @09:08PM (#11899077)
> I still don't see where you get a conflict copying the contents of a case-insensitive file system to a case-sensitive one.

Because some apps create MyFile.txt and expect to be able to access it later by myfile.txt. Adobe's applications, for example.

Re:Apple File System by bjt on Monday June 13, 2016 @11:53PM (#11899641)
I had no idea. That's horrifying.
Re:Apple File System by colejohnson66 on Tuesday June 14, 2016 @02:23AM (#11900146)
Open up the various folders of Adobe's software (on Windows). The DLLs are a mish-mash of all lowercase and upper-lower mixes. Heck, open up System32; the DLLs there are definitely not case-sensitive capable (`kbd*.dll' being one example). In fact, I bet you there's at least one program on your computer that accesses the Program Files using `C:\PROGRAM FILES (X86)' instead of `%programfiles(x86)%'. In fact, even environment variables aren't case-sensitive.