Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.linux.misc Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them Date: Fri, 2 May 2025 00:44:20 -0000 (UTC) Organization: A noiseless patient Spider Lines: 12 Message-ID: References: <20250428080014.0000347f@gmail.com> <20250428111242.00007426@gmail.com> <6813f997@news.ausics.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 02 May 2025 02:44:20 +0200 (CEST) Injection-Info: dont-email.me; posting-host="e7c4d64329c4de231a956319955b3127"; logging-data="4047725"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/1wqdp0VhdmcQSCMIxzdPW" User-Agent: Pan/0.162 (Pokrosvk) Cancel-Lock: sha1:ThTcH9TGObu2nXjJDTIrrCy9Zvc= Bytes: 1969 On 2 May 2025 08:45:44 +1000, Computer Nerd Kev wrote: > I question the wisdom of Torvalds on this topic since he allowed ext > filesystems to have an even greater evil than either of those: > newlines in file names! He was just following a *nix tradition. I think it’s probably specified in POSIX: any byte value is allowed in a file/directory name, except “/” and NUL. “/” is the separator between pathname components, and NUL is of course the string terminator. But with Unicode, I can still have filenames with “∕” in them.