From owner-freebsd-current  Fri Feb  2 15:44:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA17620
          for current-outgoing; Fri, 2 Feb 1996 15:44:49 -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 PAA17602
          for <freebsd-current@freebsd.org>; Fri, 2 Feb 1996 15:44:44 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA00880; Fri, 2 Feb 1996 16:43:35 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199602022343.QAA00880@phaeton.artisoft.com>
Subject: Re: list of major device numbers?
To: joerg_wunsch@uriah.heep.sax.de
Date: Fri, 2 Feb 1996 16:43:35 -0700 (MST)
Cc: freebsd-current@freebsd.org
In-Reply-To: <199602021005.LAA04712@uriah.heep.sax.de> from "J Wunsch" at Feb 2, 96 11:05:30 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

> > Ok, we should check this in asap, and it should probably be in 2.1
> > too or SOMEthing..
> > (so that we can keep them in sync)
> 
> What are the plans to dynamicalize the assignment of major numbers?  I
> think, except for a few ``well-known'' devices that might be important
> for the bootstrap, everything else could be handled in a dynamic
> scenario.

The plans are to replace major numbers with vnode instances generated
from device registration information and specific to the reference
instance for a given boot sequence, AFAIK.

In other words, major and minor number are to be made meaningless.

At the same time specfs will either go away entirely or be subsumed by
devfs, assuming everything works out correctly.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.