From owner-freebsd-arch@FreeBSD.ORG Tue Sep 21 10:08:04 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4028316A4CF for ; Tue, 21 Sep 2004 10:08:04 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0EC143D41 for ; Tue, 21 Sep 2004 10:08:01 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id EE1FD65458; Tue, 21 Sep 2004 11:08:00 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23118-01; Tue, 21 Sep 2004 11:08:00 +0100 (BST) Received: from empiric.dek.spc.org (adsl-67-121-95-65.dsl.snfc21.pacbell.net [67.121.95.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 9D890651F4; Tue, 21 Sep 2004 11:07:56 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 762DD6455; Tue, 21 Sep 2004 03:07:52 -0700 (PDT) Date: Tue, 21 Sep 2004 03:07:51 -0700 From: Bruce M Simpson To: Poul-Henning Kamp Message-ID: <20040921100751.GD842@empiric.icir.org> References: <46041.1095665925@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46041.1095665925@critter.freebsd.dk> cc: arch@FreeBSD.org Subject: Re: [HEADSUP] naming of tty devices. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 10:08:04 -0000 On Mon, Sep 20, 2004 at 09:38:45AM +0200, Poul-Henning Kamp wrote: > Other drivers have resorted to various variations of this scheme > (if they were copy&pasted from sio.c) or rolled their own private > naming system. In other words: it's a pretty mess right now. I've noticed the third-party software modem drivers in ports have this problem. I looked at what it would take if we were to rewrite them as uart(4) attachments and was pleasantly surprised to find it'd eliminate the reckless forking of sio(4). However, eliminating the naming inconsistency here can only be a good thing; if uart(4) can be kept in sync with these tty changes so much the better. Regards, BMS