From owner-freebsd-current Fri Jun 9 15:49:33 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 85E3D37B5A6; Fri, 9 Jun 2000 15:49:30 -0700 (PDT) Date: Fri, 9 Jun 2000 15:49:30 -0700 From: "Andrey A. Chernov" To: Kris Kennaway Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609154930.A33329@freebsd.org> References: <20000609115946.A55638@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kris@FreeBSD.org on Fri, Jun 09, 2000 at 12:58:27PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 12:58:27PM -0700, Kris Kennaway wrote: > > Bad example. Not _all_ filenames but temp. ones only which allows to run > > FreeBSD binary in MSDOS FS with MSDOS files. > > The point is the same. Files created by FreeBSD binaries during the course > of operation don't conform to an 8.3 monocase naming scheme (think of > dotfiles for example). I don't believe there's such a thing as a lowest > common denominator of file system naming conventions - either a filesystem > can support UFS names (perhaps through a translation later) or it's not > suitable for running FreeBSD from. Dotfiles usually created in user's home directory which is in UFS. What I mean is simple processing using temp files, consider running zip or unzip binaries. Proper way will be to sense FS name/abilitites and tune available charset in accordance with them. > > mktemp() makes temp files in any directory including current one. > > Yes, but in practice it's not used that way since you can't write to most > directories on the system except ~ and /tmp and relatives. I don't care about /tmp which is in UFS, I care about current directory. Probably /tmp-prefix sensing code helps to solve this. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message