From owner-freebsd-current Thu Jun 8 12:23: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id 9584F37C121 for ; Thu, 8 Jun 2000 12:22:59 -0700 (PDT) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id E949EDDB8A for ; Thu, 8 Jun 2000 15:21:17 -0400 (EDT) Message-ID: <393FF36A.8B62FB66@infolibria.com> Date: Thu, 08 Jun 2000 15:26:34 -0400 From: John LoVerso Organization: InfoLibria X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: mktemp() patch References: <20000608124605.G82993@lucifer.bart.nl> <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | >which is not believed to cause any problems with shells. The PID is also > | Some shells parse # as a deletion character if memory serves me right. > Also ^ is used for substitutions in many shells (as in ^faulty^ok). Why would you care if some shell used the a character in some special way? In general, you are not going to be typing the filename generated by mktemp() et al. And when you do, use the shell's strong quote (ala ') to escape such characters. (before someone mentions, almost none of these restrictions apply to scripts) > Symbols '=' and '+' are prohibited in some other filesystems. Specific examples of filesystems supported by FreeBSD and likely used by programs invoking mktemp(), please! (I'm not sure that the NetWare filesystem counts!) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message