in message <[EMAIL PROTECTED]>, wrote Bill Moran thusly... > > Mike Meyer wrote: > >In <[EMAIL PROTECTED]>, Walter <[EMAIL PROTECTED]> typed: > > > >>There's probably someone who can explain why non- > >>printable characters are useful in file names, but > >>I'd really rather disallow them altogether - if > >>there's a build option or control flag to set. > >>Anyone? > > > >BSD is character-set neutral. Well, it tries. The only two characters > >that are magic in file names are 0x2f and 0x00, because they both > >terminate the file name. Other than that, you are free to use whatever > >character encoding you want to. ... > What about a feature that allows an administrator to list characters > that are disallowed in filenames and directory names?
Hey, i personally would love it, but that would cause lot of troubles, for instance, when saving e-mail attachments or file generation via slrn MIME decode. in the meantime check this out (a shameless plug)... perl program... http://www103.pair.com/parv/comp/src/perl/sanename.perl documentation... http://www103.pair.com/parv/comp/src/perl/sanename.perl.pod - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message