Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!cs.utexas.edu!uunet!mcsun!hp4nl!svin02!rcpieter From: rcpieter@svin02.info.win.tue.nl (Tiggr) Newsgroups: comp.unix.wizards Subject: Re: Slashes in file names Message-ID: <1730@svin02.info.win.tue.nl> Date: 8 Feb 91 14:52:40 GMT References: <25881@adm.brl.mil> Organization: Eindhoven University of Technology, The Netherlands Lines: 18 bzs@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?