From owner-freebsd-doc@FreeBSD.ORG Mon Aug 29 16:20:28 2005 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8887316A420 for ; Mon, 29 Aug 2005 16:20:28 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 927F143D5F for ; Mon, 29 Aug 2005 16:20:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7TGKMKV070015 for ; Mon, 29 Aug 2005 16:20:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7TGKMiU070014; Mon, 29 Aug 2005 16:20:22 GMT (envelope-from gnats) Date: Mon, 29 Aug 2005 16:20:22 GMT Message-Id: <200508291620.j7TGKMiU070014@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: garys@opusnet.com (Gary W. Swearingen) Cc: Subject: Re: docs/85355: [patch] Error in the pin numbers of the described connector in the Handbook (serial). X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Gary W. Swearingen" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 16:20:28 -0000 The following reply was made to PR docs/85355; it has been noted by GNATS. From: garys@opusnet.com (Gary W. Swearingen) To: Yar Tikhiy Cc: jpeg@thilelli.net, docs@freebsd.org Subject: Re: docs/85355: [patch] Error in the pin numbers of the described connector in the Handbook (serial). Date: Mon, 29 Aug 2005 07:52:16 -0700 Yar Tikhiy writes: > It might be reasonable to tell that in general, a null-modem cable > is for connecting a DTE directly to another DTE. AFAIK, null-modem > cables can be constructed for synchronous comms, too. Then, the > topic can be narrowed down to async comms. I doubt if Julien wants to do more rewrites on the section. But I can't resist replying anyway; maybe Yar wants to rewrite it later. It probably should have some of the cable stuff from the "Serial Ports" section which says that a null-modem is AKA DTE-to-DTE cable and what DTE is, eg, a computer. And terminals traditionally have included teletypes and printers. (Once there were no CRTs or LCDs.) > To me, www.hardwarebook.net doen't seem the definite resource. > IMHO, if the topic is rather wide, the reader should better be > hinted to do a (re)search on the Net instead of pointed to a single > resource, which is likely to become incomplete, outdated, or down. I was thinking the same things. > Apropos, has there ever been a DTE printer? I think that printers > or sync comms shouldn't belong there if it were told above that we > would deal with async DTE-DTE comms only in this section. Serial printers were once common (I have one) and I think few, if any, were configured as DCE (eg, modems); the bulk were DTEs. But sync comms don't need to be mentioned; I don't know if FreeBSD can even handle it. I just wanted some note about the large number of null-modem designs for different purposes, for folks raised on USB. > We may show two or three different designs in the handbook if we > can tell the reader about their merits. The problem with the design > currently in the handbook is that it is erroneous *and* bogus. I'd > suggest adding another row to the table so that it becomes evident > that DTR on this side is connected to DSR+DCD on the other side > while DTR on the other side is connected to DSR+DCD on this side. The Note below the pin-out is supposed to make it evident, and with the Note the design is symmetric. > An RS-232 null-modem cable should be symmetric, to my mind. A "typical async null-modem cable", yes. But few of the many RS-232 null-modem cable designs shown in the book are symmetric, owing to the variety of designs of much DTE. (Less true today than yesteryear.)