

You shouldn’t consider this to be too cautious. Thanks for all the responses and thoughts.If you’re serious about safeguarding your sensitive information, password protection on your files and folders is the most sensible way to go. I appreciate all the responses I get from Something more produtive than computer games and chase I work exclusively alone and don't getįinancially compensated. I am also one who could be rightly called an amateur, orĪt least a hobbyist. This has taken me by surprise because until not it has notīeen an issue that I have had to deal with.

Other than Mac I have used BSD systems for development Linux systems (it has been a while and not a whole lotĪt that beyond using Linux for developement system). I was expecting case sensitivy when using php to locateįile name because of experience with BSD, and probably Such as using the terminal and searchs and such.

That I don't have more than profunctory experience with: However, there is A LOT to know and most of my experience With Linux systems and had several FreeBSD servers to serveĭomain names I had, from home via static ips from my ISP. I've had a chance to observe the idiosyncratic of case-sensitive vs case-insensitve up close and personal. I'm speaking as someone that has been developing and maintaining Unix file systems for 25 years, and a Mac owner for 35 years. If your access to the file system is going through a language library, it is possible the library is implementing its own rules on what is a file name match and what is not.

Many other command line commands behave the way, again because of their Unix origins. This is because the shells evolved from the Unix world of case-sensitive file systems and they do not expect to find a file under alternate spellings. Then it depends on the software doing the search.įor example the bash (and zsh) shell's if you give it a full file name (no wild cards) will just pass that to the file system and a case-insensitive lookup will occur.īut if you ask for a wild-card match, and your wildcard has the wrong case, the shell will not find the alternate spelling. However, not all access to the file system is direct, especially if you are doing a search. So if you pass the full file name to the lowest level file system calls, the macOS file system drivers will do a case- insensitive lookup. MacOS uses a case- insensitive file system.
