Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Borax Man <rotflol2@hotmail.com>
Newsgroups: comp.os.linux.misc
Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them
Date: Wed, 30 Apr 2025 10:00:01 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <slrn1013t50.1aev.rotflol2@geidiprime.bvh>
References: <pan$4068a$3910f4f1$8cbecede$9e42905e@linux.rocks>
 <20250428080014.0000347f@gmail.com> <m79tdsF2bf6U1@mid.individual.net>
 <20250428111242.00007426@gmail.com>
 <pan$c046d$e87ef491$a3427b7a$ac576dbc@linux.rocks>
 <slrn1011nu8.46v.rotflol2@geidiprime.bvh> <vurjl9$2pskn$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 30 Apr 2025 12:00:01 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="107c0e1eb3074cf4cdcb050899a40f11";
	logging-data="43323"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18tejT308l7c/i2WsdDqMQJyCyd4mIGGt4="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:S1o1pKSoar6ZyJvix2QXzGfUk+4=

On 2025-04-29, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> On Tue, 29 Apr 2025 14:18:48 -0000 (UTC), Borax Man wrote:
>
>> As for your file example though, you do demonstrate why one may choose
>> upper vs lower case, Windows does allow that.  But should they be
>> *seperate* files?
>
> It should be your choice.
>
Well, you get to choose the filesystem you use.  JFS2 if I recall could
be case insensitive, but i would play havoc with the OS if you used it
in the wron place.  In Windows, can you make it case sensitive?

>> However, I agree with your comment about unicode.  Treating upper and
>> lower case letters as the same, leads to complicated rules, which may
>> vary from system to system, and cause chaos.
>
> Unicode seems to have come up with some standard set of “default” rules 
> that are independent of any particular localization setting.

These would need to be in a standard, one that filesystems can
implement.  But then filesystems would have to implement the same
standard, otherwise, again issues arise.  Can't see this being workable
for end users.