Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them
Date: Sat, 3 May 2025 11:33:52 +0100
Organization: A little, after lunch
Lines: 63
Message-ID: <vv4reg$35qch$14@dont-email.me>
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>
 <slrn1013t50.1aev.rotflol2@geidiprime.bvh>
 <vAGdnR-Fj9qGS4_1nZ2dnZfqn_udnZ2d@giganews.com>
 <slrn1016uic.2qk.rotflol2@geidiprime.bvh> <vv24n5$rjdd$1@dont-email.me>
 <slrn1019n60.2rt.rotflol2@geidiprime.bvh>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 03 May 2025 12:33:52 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="6d7c68c55f6bdac21dbc7345acbc5505";
	logging-data="3336593"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+XKBtyYlhV0C5OC2wvhIHhWGE/yvpjcoU="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:VWIjCbaySYQpHH2Ve9BFDQL/8Y0=
Content-Language: en-GB
In-Reply-To: <slrn1019n60.2rt.rotflol2@geidiprime.bvh>
Bytes: 3972

On 02/05/2025 15:54, Borax Man wrote:
> On 2025-05-02, The Natural Philosopher <tnp@invalid.invalid> wrote:
>> On 01/05/2025 14:42, Borax Man wrote:
>>> On 2025-05-01, c186282 <c186282@nnada.net> wrote:
>>>> On 4/30/25 6:00 AM, Borax Man wrote:
>>>>> 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.
>>>>
>>>>
>>>>      So, in essence, the development of case-sensitive
>>>>      systems ruined it for case-insensitive  :-)
>>>>
>>>>      Same now for space-tolerant file names.
>>>
>>> Case sensitivity does cause problems here and there, and it was
>>> initially confusing.
>>>
>>> But spaces in filenames cause me *far more* headaches.  They are the
>>> greater evil.
>>
>> I LOVE spaces in filenames.
>> I guess if you use the command line a lot and parse file arguments using
>> spaces, its a bit irritating.
>>
>> But if you uses a GUI its no issue at all
>>
> 
> 
> Yes, I'm a command line kind of guy, and spaces are a bit of a PITA.
> Just have to remember to quote, but when you use shell expansions or
> globbing, and then things get a bit trickier.
> 
Primitive things obsoleted by a GUI :-)


-- 
"If you don’t read the news paper, you are un-informed. If you read the 
news paper, you are mis-informed."

Mark Twain