From owner-freebsd-arch@FreeBSD.ORG Tue Sep 21 10:58:33 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 493A416A4CE for ; Tue, 21 Sep 2004 10:58:33 +0000 (GMT) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B07B43D58 for ; Tue, 21 Sep 2004 10:58:32 +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 1C9idx-0002Se-UO; Tue, 21 Sep 2004 18:17:09 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.12.10/8.12.10) with ESMTP id i8LAwfoI083254; Tue, 21 Sep 2004 17:58:41 +0700 (NOVST) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.12.10/8.12.10/Submit) id i8LAwdQ6083215; Tue, 21 Sep 2004 17:58:39 +0700 (NOVST) (envelope-from danfe) Date: Tue, 21 Sep 2004 17:58:39 +0700 From: Alexey Dokuchaev To: Poul-Henning Kamp Message-ID: <20040921105839.GA82522@regency.nsu.ru> References: <20040921104246.GA75823@regency.nsu.ru> <42228.1095763864@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42228.1095763864@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:58:33 -0000 On Tue, Sep 21, 2004 at 12:51:04PM +0200, Poul-Henning Kamp wrote: > In message <20040921104246.GA75823@regency.nsu.ru>, Alexey Dokuchaev writes: > >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. > > The problem with just a 'i' or 'l' is that it creates confusion as to > what is the device name and what is the extension. I like the concept > of a big fat '.' in there to tell the extension apart. Shortening the > extension from "init" to "i" and "lock" to "l" would be confusing at > best, and of little real saving in practice. > > My plan is for the ".init" and ".lock" devices to be "on-demand", in > other words, they won't show up until first time you try to access them. Sounds fair enough. Thanks! ./danfe