From owner-freebsd-arch Wed Oct 6 9:49:50 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 2F9641570E for ; Wed, 6 Oct 1999 09:49:28 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id SAA22425 for ; Wed, 6 Oct 1999 18:49:22 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA26749 for freebsd-arch@freebsd.org; Wed, 6 Oct 1999 18:49:21 +0200 (MET DST) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id 8BFC515708 for ; Wed, 6 Oct 1999 09:48:57 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 6707 invoked from network); 6 Oct 1999 16:48:53 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 6 Oct 1999 16:48:53 -0000 Message-ID: <37FB7D75.1A413D00@simon-shapiro.org> Date: Wed, 06 Oct 1999 12:48:53 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: arch@freebsd.org Subject: Re: Minor Device numbers References: <37FA70B9.B5DBA345@simon-shapiro.org> <37FB29E3.94672E74@newsguy.com> Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Simon Shapiro as Himself wrote: > > > > I am open to any polite suggestion, but my inclination > > is to recommend 32bit major devices where the lower > > 8 bits do exactly what they do today, and the upper > > 24 are as per driver. The problem with that is that > > the major number is stuck in the middle of the minor. > > Actually was the upper byte on the PDP-11 :-). > > To solve that one would need either separate arguments, > > or turn dev_t to a 64bit integer. > > Well, I'd like devfs people to correct me if I'm incorrect, but... > > It is my impression that devfs solves your problem, to a certain > extent. As devices get their numbers as they come and go, there is > no need to reserve ranges to specific devices. I wouldn't mind > someone taking this opportunity to explain exactly how devfs deals > with this. :-) This does not help production people like me who want 3.x support and many more who actually want 2.2 support. > Now, the main point of this message... the solution to all of dev's > problem is devfs (axiom). As a result, nobody is going to help with > work-arounds to your problem, since the correct solution is devfs. > Or, in other words, until devfs comes along, you are not getting a > solution to your problem. :-( > > Furthermore, I'm not sure devfs/slice can get into the tree before > RELENG_4 comes along, and that would delay it, and anything > depending on it, until 5.0-RELEASE! Frankly, that's a scenario I'd > rather avoid. I think we'll be seriously impaired if we delay devfs > further. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "I always feel generous when I'm in the inner circle of a > conspiracy to subvert the world order and, with a small group of > allies, just defeated an alien invasion. Maybe I should value myself > a little more?" -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message