Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!news.nobody.at!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Carlos E.R." <robin_listas@es.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them
Date: Sat, 3 May 2025 13:52:51 +0200
Lines: 59
Message-ID: <jlchelx0p6.ln2@Telcontar.valinor>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net qyooxjtjmJp1NAmhOEr9NwPP6q3N5NZ/+/3gHgH5HxBuLNMe6e
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:O5O9NSG6s5dpxjZ068PbeNQoXlQ= sha256:f16t4sOH7HGtcyuzMSihfGy91qvrO8JVwBUvp6XDl4Y=
User-Agent: Mozilla Thunderbird
Content-Language: es-ES, en-CA
In-Reply-To: <vv24n5$rjdd$1@dont-email.me>

On 2025-05-02 11:53, The Natural Philosopher 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
> 

Same here.

And yes, I do scripts and it complicates them. Still... it makes 
filenames more readable. Book names, movie names, document names... I 
also like the colon ":" in filenames. It runs havoc with Windows users, 
though :-)

-- 
Cheers, Carlos.