From owner-freebsd-arch@FreeBSD.ORG Tue Sep 21 10:42:43 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 250E116A4CE for ; Tue, 21 Sep 2004 10:42:43 +0000 (GMT) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42B8943D49 for ; Tue, 21 Sep 2004 10:42:42 +0000 (GMT) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.34) id 1C9iOa-0001Dj-30; Tue, 21 Sep 2004 18:01:16 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.12.10/8.12.10) with ESMTP id i8LAgmoI077808; Tue, 21 Sep 2004 17:42:48 +0700 (NOVST) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.12.10/8.12.10/Submit) id i8LAgkxK077724; Tue, 21 Sep 2004 17:42:46 +0700 (NOVST) (envelope-from danfe) Date: Tue, 21 Sep 2004 17:42:46 +0700 From: Alexey Dokuchaev To: Poul-Henning Kamp Message-ID: <20040921104246.GA75823@regency.nsu.ru> 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> User-Agent: Mutt/1.4.2.1i 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:42:43 -0000 On Mon, Sep 20, 2004 at 09:38:45AM +0200, Poul-Henning Kamp wrote: > > My suggestion is the following: > > All drivers will offer "tty${something}" devices, and > generally ${something} will consist of a letter followed > by a number, possibly in base 36 ([0-9a-z]). > > All drivers which attach to external equipment via a serial > connector should also offer "cua${thesamething}". "Embedded" > serial ports, pseudo drivers etc, do not have to offer the > "cua" if DCD state on open is not an issue. > > The init and lock devices will be called ${base_device}.[init,lock] > and they will possibly be provided by on-demand devices so that > they do not clutter up /dev. What about contracting `.init|lock' to just `i|l', like we have with all (most) other device names out there (i.e., acd0t0, not acd0track0) -- long device names is a thing to avoid, IMHO. ./danfe