From owner-freebsd-questions@freebsd.org Mon Oct 10 22:22:53 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 141E7C0C019 for ; Mon, 10 Oct 2016 22:22:53 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB193311 for ; Mon, 10 Oct 2016 22:22:52 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-117-205.dynamic.qsc.de [92.195.117.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 5E4CF24D6E for ; Tue, 11 Oct 2016 00:22:50 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u9AMMo9V002125 for ; Tue, 11 Oct 2016 00:22:50 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 11 Oct 2016 00:22:50 +0200 From: Polytropon To: freebsd-questions@freebsd.org Subject: Re: Call-out ports renamed cuadX -> cuauX -- when? Message-Id: <20161011002250.067f2b85.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 22:22:53 -0000 On Mon, 10 Oct 2016 20:49:50 +0300, Boris Samorodov wrote: > Hi All, > > I've just came across this text at TFH (25.2.1. Serial Cables and > Ports): > --- > Call-out ports are named /dev/cuauN on FreeBSD versions 10.x and higher > and /dev/cuadN on FreeBSD versions 9.x and lower. > --- > > Seems not to be true. My 9.3-STABLE machine has cuau*: > --- > % uname -a > FreeBSD uni.wart.ru 9.3-STABLE FreeBSD 9.3-STABLE #0 r306337: Mon Sep 26 > 19:56:26 MSK 2016 bsam@uni.wart.ru:/usr/obj/usr/src/sys/GENERIC i386 > % % ls -l /dev/cua* > crw-rw---- 1 uucp dialer 0x29 26 сен 22:04 /dev/cuau0 > crw-rw---- 1 uucp dialer 0x2a 26 сен 22:04 /dev/cuau0.init > crw-rw---- 1 uucp dialer 0x2b 26 сен 22:04 /dev/cuau0.lock > --- Same on my FreeBSD 8 home system: % ll /dev/cua* crw-rw---- 1 uucp dialer 0, 49 2016-10-10 23:49:07 /dev/cuau0 crw-rw---- 1 uucp dialer 0, 50 2016-10-10 23:49:07 /dev/cuau0.init crw-rw---- 1 uucp dialer 0, 51 2016-10-10 23:49:07 /dev/cuau0.lock > I failed to find the reference commit. Can someone recall when did the > change occure? It probably has happened somewhere in v11... The Thinkpad laptop running 10.3 I have here, connected to the "dock" with a serial port, also shows the cucu0 device similar to your listing. Maybe the cuad0 port gets created dynamically somehow? In fact, I cannot remember having seen cuad0 anywhere... even worse, on older FreeBSD versions, cuaa0 was the port name used for modems or mice, if I remember correctly... So maybe it's just a "multi-typo"? ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...