From owner-freebsd-current Sat Feb 3 13:52:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA04533 for current-outgoing; Sat, 3 Feb 1996 13:52:18 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA04523 for ; Sat, 3 Feb 1996 13:52:16 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA04419; Sat, 3 Feb 1996 14:50:46 -0700 From: Terry Lambert Message-Id: <199602032150.OAA04419@phaeton.artisoft.com> Subject: Re: list of major device numbers? To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 3 Feb 1996 14:50:46 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199602030816.JAA08609@uriah.heep.sax.de> from "J Wunsch" at Feb 3, 96 09:16:40 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > > > What are the plans to dynamicalize the assignment of major numbers? I > > > if you specify (-1?) it will dynamically assign you one, > > but I need to change this so that it statrs at a higher number > > so as to not collide with devices that already statically > > have a spot.. > > So we should reserve the first 20 numbers for fixed ones, and convert > all but the critical drivers to no longer using a fixed one. Should > we? We should be using vnode struct addresses instead of major/minor numbers internally to the kernel. For boot-critical drivers, the correct method is not to assign a particular lexical offset to the critical drivers (since this implies a lexically based lookup, and we want to kill that). Major and minor numbers need to die. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.