From owner-freebsd-arch Mon Jun 26 17: 2: 0 2000 Delivered-To: freebsd-arch@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id 9211E37BA93 for ; Mon, 26 Jun 2000 17:01:57 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id RAA55820; Mon, 26 Jun 2000 17:01:56 -0700 (PDT) Message-ID: <20000626170155.54803@hydrogen.funkthat.com> Date: Mon, 26 Jun 2000 17:01:55 -0700 From: John-Mark Gurney To: Alfred Perlstein Cc: arch@freebsd.org Subject: Re: dynamic filetypes. please comment. References: <20000626142428.A275@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <20000626142428.A275@fw.wintelcom.net>; from Alfred Perlstein on Mon, Jun 26, 2000 at 02:24:28PM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein scribbled this message on Jun 26: > This idea leads us to a generic api for seqeunce number generation > that we can use when a subsystem needs an increasing unique number, > the api would look something like: > > (void)sequence_register("filetypes", starting_number); > mynum = sequence_next("filetypes"); /* to be used for f_type */ shouldn't we use newbus for this? and treat this like device driver assignment? we can "wire" down filetypes numbers using the same method that drivers are wired down with... Inventing another interface for one that already exists seems redundant.. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message