From owner-freebsd-current Sat Jun 10 9:39:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 47EBD37BBF9; Sat, 10 Jun 2000 09:39:53 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p61-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.62]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id BAA08158; Sun, 11 Jun 2000 01:39:50 +0900 (JST) Message-ID: <394267EB.F56153D5@newsguy.com> Date: Sun, 11 Jun 2000 01:08:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > Instead of using only alphabetic characters, the patch uses the following > character set: > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > > which is not believed to cause any problems with shells. The PID is also Huh? # does not cause problems? : does not cause problems? Mind you, shells don't have problems with any character at all in a filename if they are properly written, but if you are expecting the filenames generated by mktemp() to be handled by shell, they ought to pass the IFS=':'; for file in $filelist test. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@yet.another.bsdconspiracy.org Hmmm - I have to go check this. My reality assumptions are shattered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message