From owner-freebsd-hackers Wed Aug 30 11:33:58 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA19949 for hackers-outgoing; Wed, 30 Aug 1995 11:33:58 -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 LAA19941 for ; Wed, 30 Aug 1995 11:33:55 -0700 Received: from ris1.UUCP (ficc@localhost) by uuneo.neosoft.com (8.6.10/8.6.10) with UUCP id NAA05332 for freebsd.org!hackers; Wed, 30 Aug 1995 13:24:02 -0500 Received: by ris1.nmti.com (smail2.5) id AA06978; 30 Aug 95 11:11:02 CDT (Wed) Received: by sonic.nmti.com; id AA11762; Wed, 30 Aug 1995 11:37:06 -0500 From: peter@nmti.com (Peter da Silva) Message-Id: <9508301637.AA11762@sonic.nmti.com.nmti.com> Subject: Re: Gritching about XFree86 and serial port naming To: bde@zeta.org.au (Bruce Evans) Date: Wed, 30 Aug 1995 11:37:05 -0500 (CDT) Cc: hackers@freebsd.org, peter@nmti.com In-Reply-To: <199508300107.LAA10577@godzilla.zeta.org.au> from "Bruce Evans" at Aug 30, 95 11:07:16 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1659 Sender: hackers-owner@freebsd.org Precedence: bulk > >Why, oh why, is the CU device for "ttyd0" called "cuaa0" instead of "cuad0"? > >Or making it ttya0? > It was to give a unique name when the name is truncated to 2 characters > for printing by ps, etc. That I understand. What I don't understand is why you changed: tty00 to ttyd0 but: cua00 to cuaa0 ??? What's wrong with "ttya0" or "cuad0"? > When did they make sense? They were never called sio* or ttys*. Under 386BSD they were. > `s' > would have been a bad name anyway since sio is actually the ns(x)xx50 > driver. This point becomes more important when there are half a dozen > other Serial IO drivers with different broken naming schemes. Yes, that's another can of worms I'd like to open at another time. Along with the broken programs that assume the ttyXX pattern. > >For 2.1, can we go back to at least making the tty and cua devices have the > >same identifiers? > When did they have the same identifiers? If you say that tty00 and cua00 > have the same identifiers, then I'll say that `0' is not an identifier :-). Oh, don't be silly. You know what I mean. "00" and "00" for COM1 make sense. "d0" and "d0" make less sense, but still work. "d0" and "a0" are just plain weird. > That would be bogus. X works with the vanilla POSIX port ttyd0 and > always has. Fine. Then the XFree86 setup needs to use that instead of /dev/mouse. You're looking at it from the point of view of someone who knows what all this stuff does. I'm dealing with someone who doesn't and wants to learn, and only comes to me when something's broke. That's good. That's the sort of people we want to encourage. All this inconsistency makes it harder.