From owner-freebsd-doc@FreeBSD.ORG Thu May 15 16:33:11 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41642546; Thu, 15 May 2014 16:33:11 +0000 (UTC) Received: from gullfoss.araneus.fi (gullfoss.araneus.fi [151.236.24.64]) by mx1.freebsd.org (Postfix) with ESMTP id ADAD72962; Thu, 15 May 2014 16:33:10 +0000 (UTC) Received: from gunvor.araneus.fi (gunvor.araneus.fi [46.246.126.150]) by gullfoss.araneus.fi (Postfix) with ESMTP id 426573C24E; Thu, 15 May 2014 16:26:50 +0000 (UTC) Received: from guava.gson.org (unknown [10.0.1.240]) by gunvor.araneus.fi (Postfix) with ESMTP id 57C6514567F; Thu, 15 May 2014 16:26:43 +0000 (UTC) Received: by guava.gson.org (Postfix, from userid 101) id 5739775E33; Thu, 15 May 2014 19:26:48 +0300 (EEST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <21364.60104.310659.351880@guava.gson.org> Date: Thu, 15 May 2014 19:26:48 +0300 To: gavin@FreeBSD.org Subject: Re: docs/175560: ugen(4) man page contains incorrect device node path In-Reply-To: <201405151450.s4FEo8uZ035711@freefall.freebsd.org> References: <201405151450.s4FEo8uZ035711@freefall.freebsd.org> X-Mailer: VM 8.0.14 under 21.4.1 (i386--netbsdelf) From: Andreas Gustafsson Cc: freebsd-doc@FreeBSD.org, gson@gson.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2014 16:33:11 -0000 Hi, gavin@FreeBSD.org wrote: > Synopsis: ugen(4) man page contains incorrect device node path > > State-Changed-From-To: open->feedback > State-Changed-By: gavin > State-Changed-When: Thu May 15 13:26:42 UTC 2014 > State-Changed-Why: > Hi, and sorry for the delay in responding to this. The issue is that > the endpoint ID will be a single digit for endpoints 0-9, and double > digits for enpoint 10 and up. I'm not sure it's worth changing the > man page to reflect that both of these are possible, do you have any > opinion? I'm coming to this from NetBSD, where the endpoint number always consists of two digits. For example, endpoint 0 of device 0 is called /dev/ugen0.00, not /dev/ugen0.0. When I tried to open a ugen endpoint on a FreeBSD system using the same device path I had used on NetBSD, it failed as the device node did not exist. Reading the FreeBSD ugen man page then only added to my confusion, because the pattern "/dev/ugenN.EE" in the man page seemed to exactly match the name that did not work. The FreeBSD ugen device and its man page are derived from the NetBSD ones. I'm not sure why FreeBSD is using a naming scheme incompatible with that of NetBSD, but if this is a deliberate change, then surely the man page should also be changed accordingly. At a minimum, it could be changed to simply say: /dev/ugenN.E Endpoint E of device N. Presumably N can also be larger than 9, and if a single N can denote an multi-digit integer, so can a single E. -- Andreas Gustafsson, gson@gson.org