Tmpfs Adding Case Insensitive Support For Wine / Steam Play & Flatpaks

[phoronix]

Phoronix: Tmpfs Adding Case Insensitive Support For Wine / Steam Play & Flatpaks

In addition to the EXT4 and XFS atomic write support, another interesting pull request sent in today by Microsoft's Christian Brauner is adding case-insensitive file/folder support for the Tmpfs file-system to benefit use-cases like Wine / Steam Play compatibility layers and sandboxing/container facilities like Flatpak...

https://www.phoronix.com/news/Linux-6.13-Tmpfs-Case-Folding

[Spacefish]

Honestly, microsoft should just move to get rid of case-insensivity by default.

like disabling case-insensitivity on a file system level and only enable it on some specific folders for software not explicitly targeting newer / future windows versions.
Much like they introduces long-path support..

Later on maybe offer an compability mode on API level to make open calls case-insensitive only for some processes.

NTFS can already enable/disable case-sensitivity on a per folder basis, so why not start to migrate to case-sensitive like any other OS out there long term..

Would avoid funny problems with git as well, where the repo contains different files which just differ by case and windows override one with the other in the working dir, when checking out the repo

[Quackdoc]

Honestly, microsoft should just move to get rid of case-insensivity by default.

like disabling case-insensitivity on a file system level and only enable it on some specific folders for software not explicitly targeting newer / future windows versions.
Much like they introduces long-path support..

Later on maybe offer an compability mode on API level to make open calls case-insensitive only for some processes.

NTFS can already enable/disable case-sensitivity on a per folder basis, so why not start to migrate to case-sensitive like any other OS out there long term..

Would avoid funny problems with git as well, where the repo contains different files which just differ by case and windows override one with the other in the working dir, when checking out the repo

no, case insensitivity is what most people prefer, and there is very little benefits to having case sensitivity for the vast majority of normal users.

[skeevy420]

no, case insensitivity is what most people prefer, and there is very little benefits to having case sensitivity for the vast majority of normal users.

That's pretty funny coming from the person not capitalizing words . I prefer sensitivity ... until I'm on Linux and I extract an archive created on Windows with things named using a combination of CaMeL CaSe, ALL CAPS, all lower, and EveRy 0tH3r Fuck3d up way under the sun. We clearly have our own biases on this subject , though I do agree about it having little benefit for the vast majority of normal users.

Back in the day I learned via Windows archives that XFCE has a really badass batch renaming tool built into Thunar. Damn I miss that batch rename ability and I wish KDE had it.

[Fullmetal5]

Honestly, microsoft should just move to get rid of case-insensivity by default.

like disabling case-insensitivity on a file system level and only enable it on some specific folders for software not explicitly targeting newer / future windows versions.
Much like they introduces long-path support..

Later on maybe offer an compability mode on API level to make open calls case-insensitive only for some processes.

NTFS can already enable/disable case-sensitivity on a per folder basis, so why not start to migrate to case-sensitive like any other OS out there long term..

Would avoid funny problems with git as well, where the repo contains different files which just differ by case and windows override one with the other in the working dir, when checking out the repo

I can't imagine the amount of vulnerabilities that would make even in Windows itself. If you take a look at ProcMon you'll see just how many Microsoft programs alone hardcode paths like C:\WINDOWS and the like. Even having it be an opt-in probably wouldn't be enough given the likely hood of missing hardcoded paths somewhere in existing programs that would result in a long game of wack-a-mole to fix over a course of years. While I would like for it to be case-senesitive as well I just don't know if it's realistic at this point.

[Quackdoc]

That's pretty funny coming from the person not capitalizing words . I prefer sensitivity ... until I'm on Linux and I extract an archive created on Windows with things named using a combination of CaMeL CaSe, ALL CAPS, all lower, and EveRy 0tH3r Fuck3d up way under the sun. We clearly have our own biases on this subject , though I do agree about it having little benefit for the vast majority of normal users.

Back in the day I learned via Windows archives that XFCE has a really badass batch renaming tool built into Thunar. Damn I miss that batch rename ability and I wish KDE had it.

me arms and wrists hurt too much to bother with capitalization , once I finally find a useful speech to text tool for linux, I'll have some of the best capitalization AND punctuation on here assuming the tool is good lol.

[Danny3]

Isn't this folder common use for other processes than WINE / Proton too?
Isn't another way to solve this?
I think Linux is right with having case sensitive filesystems and searchers by default!
The case-insesitive searches should be done on top of that.

[pWe00Iri3e7Z9lHOX2Qx]

Honestly, microsoft should just move to get rid of case-insensivity by default.

like disabling case-insensitivity on a file system level and only enable it on some specific folders for software not explicitly targeting newer / future windows versions.
Much like they introduces long-path support..

Later on maybe offer an compability mode on API level to make open calls case-insensitive only for some processes.

NTFS can already enable/disable case-sensitivity on a per folder basis, so why not start to migrate to case-sensitive like any other OS out there long term..

Would avoid funny problems with git as well, where the repo contains different files which just differ by case and windows override one with the other in the working dir, when checking out the repo

The number of times in my life that I've really wanted a bunch of files in a folder with the same name but different casing has been zero.

[ssokolow]

Isn't this folder common use for other processes than WINE / Proton too?
Isn't another way to solve this?
I think Linux is right with having case sensitive filesystems and searchers by default!
The case-insesitive searches should be done on top of that.

Not /tmp, tmpfs... it's a building block.

ssokolow@monolith-tng ~ % mount | grep ' tmpfs'
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6492452k,mode=755,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
tmpfs on /run/qemu type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
tmpfs on /run/firejail/dbus type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6492452k,mode=755,inode64)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=6492448k,nr_inodes=1623112,mode=700,uid=1000,gid=1000,inode64)
​

This is adding an option so that things like Flatpak, which use it as the basis for constructing the view of the filesystem that sandboxed apps see, can request that the instances they construct be case-insensitive.

[skeevy420]

me arms and wrists hurt too much to bother with capitalization , once I finally find a useful speech to text tool for linux, I'll have some of the best capitalization AND punctuation on here assuming the tool is good lol.

I hear you there. I haven't played any bass for a few years because I've made the mistake of falling and catching myself a few too many times in life. I tried to get back into it during COVID but it hurts to fret notes on my left hand or to do anything other than using a pick with my right hand.