From owner-freebsd-hackers Fri Sep 1 11:38:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA13021 for hackers-outgoing; Fri, 1 Sep 1995 11:38:34 -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 LAA13014 for ; Fri, 1 Sep 1995 11:38:33 -0700 Received: from ris1.UUCP (ficc@localhost) by uuneo.neosoft.com (8.6.10/8.6.10) with UUCP id NAA26341; Fri, 1 Sep 1995 13:23:33 -0500 Received: by ris1.nmti.com (smail2.5) id AA14790; 1 Sep 95 12:21:09 CDT (Fri) Received: by sonic.nmti.com; id AA26461; Fri, 1 Sep 1995 12:47:16 -0500 From: peter@nmti.com (Peter da Silva) Message-Id: <9509011747.AA26461@sonic.nmti.com.nmti.com> Subject: Re: Gritching about XFree86 and serial port naming To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Fri, 1 Sep 1995 12:47:16 -0500 (CDT) In-Reply-To: <199509011637.LAA09120@brasil.moneng.mei.com> from "Joe Greco" at Sep 1, 95 11:37:33 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1706 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > tty[a-?][0-9a-z] for callout > > tty[A-?][0-9A-Z] for callin > Why use tty for callout? You are killing the potential ranges of tty names. Huh? Got the same number of tty devices as the current scheme. Personally I prefer tty[a-?]{0,1,2,3,4,5,6,7,8,9,10,...} tty[a-?]{0,1,2,3,4,5,6,7,8,9,10,...}.cu tty[a-?]{0,1,2,3,4,5,6,7,8,9,10,...}.ctl tty[a-?]{0,1,2,3,4,5,6,7,8,9,10,...}.lck And increasing the width of the fields in ps and so on. > It's also not quite as immediately obvious that "ttyBZ" and "ttybz" are > paired, and which one plays which role. It's obvious they're paired. Which plays which role is less obvious, I agree. tty[0-9a-oA-Z][0-9a-z]{,.cu,.ctl,.lck} would be cleaner, anyway. > "ttybz" and "cuabz" seems more intuitive to me... Just so long as it's the same "bz". > Part of what we should be thinking of, IMHO, is how people manage these > large numbers of ports, and work the naming scheme around that. As I said, > I would really like to see cards done somehow on letter boundaries such that > I can simply label a breakout box as "tty2*" and if an operator should come > looking for a malfunctioning line, they don't need to come find me to > decipher which box and which line "tty27" is. The people who are managing > small numbers of serial ports really don't give a damn, but this would be > very helpful to large installations! The system our old modem server used was 3 digits, with multiple expansion boxes on a baseband cable (not ethernet, but similar technology) ttymXYZ X = 0-7 card # Y = 0-7 box # Z = 0-7 or 0-F port # Really, the System V naming schemes make more sense. If you had 20 fredport boards, you could make it ttyf[0-j][0-9].