macOS 13.5 no longer allows setting system wide ulimits

Re:macOS 13.5 no longer allows setting system wide ulimits by fouc on Wednesday August 23, 2023 @07:50AM (#37234457)

use & support asahi linux

[ Parent | on HN ]

Re:macOS 13.5 no longer allows setting system wide ulimits by DarkmSparks on Wednesday August 23, 2023 @07:55AM (#37234510)

I support asahi linux.

But Apple should generally fix this. Having a system wide limit of 256 files open is almost as outdated and idiotic as having a filesystem that doesnt support case or more than 256 characters (NTFS)

[ Parent | on HN ]

Re:macOS 13.5 no longer allows setting system wide ulimits by mnd999 on Wednesday August 23, 2023 @08:25AM (#37234792)

NTFS does support case internally.

[ Parent | on HN ]

Re:macOS 13.5 no longer allows setting system wide ulimits by thfuran on Wednesday August 23, 2023 @08:34AM (#37234885)

And windows now supports longer paths, but I think it's still disabled by default (and I'm sure there's a bunch of legacy software that is still using old APIs and can't support long paths anyways).

[ Parent | on HN ]

Re:macOS 13.5 no longer allows setting system wide ulimits by mort96 on Wednesday August 23, 2023 @08:47AM (#37234987)

Windows Explorer itself is an example of such "legacy software".

[ Parent | on HN ]

Re:macOS 13.5 no longer allows setting system wide ulimits by nullindividual on Wednesday August 23, 2023 @08:51AM (#37235036)

The limit was with Win32. It’s not a “legacy” API, but it is as old as NT. There are some applications which do not use the MAX_PATH constant, such as Office (probably one of the few rate examples; Office apps have some horrid hacks like this and how they paint their menu bar).

Case sensitivity will break certain applications.

[ Parent | on HN ]