You are viewing a single thread.
View all comments View context
11 points

Why would case sensitive path names be considered dangerous?

permalink
report
parent
reply
1 point
Deleted by creator
permalink
report
parent
reply
12 points
*

I don’t know about dangerous, but case-insensitive Unicode comparison is annoying, expensive and probably prone to footguns compared to a simple byte-for-byte equality check.

Obviously, it can be done, but I guess Linux devs don’t consider it worthwhile.

(And yes, all modern filesystems support Unicode. Linux stores them as arbitrary bytes, Apple’s HFS uses… some special bullshit, and Windows uses UTF-16.)

permalink
report
parent
reply
1 point

so if linux stores file names as arbitrary bytes them could I modify a ext4 fs to include a / in a file name

permalink
report
parent
reply
1 point

If you did it would likely break something as it’s one of only two characters not allowed in a file name (the other being null).

You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos!

permalink
report
parent
reply
1 point

Meanwhile fishshell:

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 3.7K

    Monthly active users

  • 1.1K

    Posts

  • 39K

    Comments