From owner-freebsd-hackers  Fri Sep  1 11:38:30 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA12999
          for hackers-outgoing; Fri, 1 Sep 1995 11:38:30 -0700
Received: from uuneo.neosoft.com (uuneo.NeoSoft.COM [198.64.84.252])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id LAA12993
          for <hackers@freebsd.org>; Fri, 1 Sep 1995 11:38:29 -0700
Received: from ris1.UUCP (ficc@localhost) by uuneo.neosoft.com (8.6.10/8.6.10) with UUCP id NAA26344 for freebsd.org!hackers; Fri, 1 Sep 1995 13:23:35 -0500
Received: by ris1.nmti.com (smail2.5)
	id AA14909; 1 Sep 95 12:26:36 CDT (Fri)
Received: by sonic.nmti.com; id AA26697; Fri, 1 Sep 1995 12:52:43 -0500
From: peter@nmti.com (Peter da Silva)
Message-Id: <9509011752.AA26697@sonic.nmti.com.nmti.com>
Subject: Re: Gritching about serial port naming, plus Digiboard driver Q...
To: jgreco@brasil.moneng.mei.com (Joe Greco)
Date: Fri, 1 Sep 1995 12:52:43 -0500 (CDT)
Cc: peter@nmti.com, hackers@freebsd.org
In-Reply-To: <199509011653.LAA09161@brasil.moneng.mei.com> from "Joe Greco" at Sep 1, 95 11:53:18 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 586       
Sender: hackers-owner@freebsd.org
Precedence: bulk

> Yes, this is entirely true.  I am thinking about this more from an
> administrative point of view, I suppose....  but then again, how do you deal
> with the case where somebody has installed

> com1/com2 as tty00-01 minor #s 0,1
> BB2016 as tty10-1f minor #s 2-17

> and then decides to install com3/4 as tty02-03?

mknod tty02 c maj 18
mknod tty03 c maj 19

> With the recent minor number range expansion, maybe it would make sense to
> assign something like 64 or 256 ports per letter, and just be done with it
> all...?

That would work, too. And would encourage wider port names.