Interoperability is a key concern. What if I mount such a filesystem? I could try to 'correct' the file name (drop or fix chars), have a fallback representation (hexencode). I could move the inode to /lost+found as corrupted or return EIO.
I think it was just the default behavior from not-thinking-about-it. Certainly control chars (including newline) could have been forbidden without restricting character encoding since all legacy encodings were careful to avoid overlapping with control bytes.
-
-
English is Torvalds' second language. Despite multiple japanese courses/books/videos, I've still just got one.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.