From owner-freebsd-current Fri Jun 9 23: 5:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0AB3337C2D3; Fri, 9 Jun 2000 23:05:13 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA08614; Sat, 10 Jun 2000 16:05:06 +1000 Date: Sat, 10 Jun 2000 16:05:02 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: "Andrey A. Chernov" , Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Jun 2000, Kris Kennaway wrote: > 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. There is the POSIX.1 portable filename character set: [A-Za-z._-] (from which the hyphen shall not be used as the first character of a portable filename). There are the POSIX NAME_MAX and pathconf(path, _SC_NAME_MAX) test features. NAME_MAX may be as low as 14 on POSIX systems. It is a small step from 14 to 11 or 8 to support non-POSIX 8.3 filenames. Very few programs actually support systems with variable or short filenames. patch(1) is one. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message