From owner-freebsd-questions Wed Feb 5 21:48:13 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 627E337B401 for ; Wed, 5 Feb 2003 21:48:11 -0800 (PST) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419EB43FAF for ; Wed, 5 Feb 2003 21:48:11 -0800 (PST) (envelope-from parv_fm@mailsent.net) Received: from sdn-ap-022dcwashp0020.dialsprint.net ([63.191.160.20] helo=moo.holy.cow) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18getM-0001uD-00; Wed, 05 Feb 2003 21:48:09 -0800 Received: by moo.holy.cow (Postfix, from userid 1001) id 1E1FEC2D0; Thu, 6 Feb 2003 00:51:08 -0500 (EST) Date: Thu, 6 Feb 2003 00:51:07 -0500 From: parv To: Bill Moran Cc: Walter , Questions Subject: Re: handling non-printable characters in file names Message-ID: <20030206055107.GA317@moo.holy.cow> Mail-Followup-To: Bill Moran , Walter , Questions References: <3E41A24E.9090607@earthlink.net> <15937.47061.743702.496178@guru.mired.org> <3E41BD21.9020508@potentialtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E41BD21.9020508@potentialtech.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG in message <3E41BD21.9020508@potentialtech.com>, wrote Bill Moran thusly... > > Mike Meyer wrote: > >In <3E41A24E.9090607@earthlink.net>, Walter 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 majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message