Barry Karas said:
Right, they're disallowed. But why - and how can the restrictions be
overcome?
Well, how do YOU specify the path to a file? The rest of us using Windows
use something like C:\path\file. Guess you don't know about UNCs used to
specify networked resources, like shared folders, such as //hostname/path.
You don't get to use slashes because they have a specific use. You don't
get to use * or ?, either, because those are wildcards. In Unix, you *can*
use all characters but most users cannot: they get to use what their command
interpreter permits because some are designated for special use (just like
in Windows) so using those characters requires an app that can directly
enter the characters in the file system rather than through a UI.
You can't because you can't. I don't recall a single operating system that
lets you use every possible character in a path for filename. Why? Because
they want to provide additional features that require identifying those
features with special characters. Would you like to revert back to a file
system where the only path was root and you had to pile all your thousands
of files into that one path?