From owner-freebsd-hackers Sun Jun 27 18: 0:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 2754214D21 for ; Sun, 27 Jun 1999 18:00:09 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA05702; Sun, 27 Jun 1999 21:00:08 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA03854; Sun, 27 Jun 1999 21:00:07 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 21:00:07 -0400 (EDT) From: Alexander Viro To: Doug Rabson Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Doug Rabson wrote: > I'm talking about the concept of a header file containing something like: > > #define FL_VFS 0 > #define FL_FOOFS 1 > #define FD_BARFS 2 > ... > > not being scalable. > > Do you have a complete list of filesystem types? Are you prepared to act > as an Assigned Number authority for that list. For this kind of problem, > strings are a damn sight easier to manage in the long term. Augh... It's ugly, indeed, but... sysctl() is not much nicer and all systems in question manage to deal with it somehow. OTOH doing it as strings... Hell knows. I'll look at it. Considering that HFS folks had already asked for more than one value here (creator and type?) it may be reasonable. I'm afraid that doing that may open the hell gates ;-/ 'N' in *ANA can be 'namespace' as well as 'number'... [1] BTW, how does NetBSD deal with HFS forks? [1] cue current flamew^Wthreads on l-k regarding files-as-directories hell. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message