Slashes in file names

[Tiggr]

bzs at world.std.com (Barry Shein) writes:

>So, for example, "Expense Report 2/30/91" could be stored on Unix as
>"Expense Report 2##30##91" or some such thing, and the appropriate
>warning about file name length limitations (slashes count as two
>characters) could be issued. Whatever. They'd then be read back and
>the slashes re-inserted, and everyone lives happily ever after.

And then you log on to your UNIX machine and then *surprise* you see a
funny name.  You don't want conversion be done by the server, but by
the client; the server could (in case of a UNIX server) simply reject
names containing `/' characters (reporting: `No such file or
directory').  In general it isn't difficult to choose a different
name after having seen this error.

Tiggr
--
Doesn't fsck(1) remove `/' characters from directory entries?