From owner-svn-doc-all@FreeBSD.ORG Tue May 6 19:45:13 2014 Return-Path: Delivered-To: svn-doc-all@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 20E3A806; Tue, 6 May 2014 19:45:13 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00507B9B; Tue, 6 May 2014 19:45:13 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s46JjCFE095240; Tue, 6 May 2014 19:45:12 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s46JjCIJ095239; Tue, 6 May 2014 19:45:12 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405061945.s46JjCIJ095239@svn.freebsd.org> From: Dru Lavigne Date: Tue, 6 May 2014 19:45:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44779 - head/en_US.ISO8859-1/books/handbook/serialcomms X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2014 19:45:13 -0000 Author: dru Date: Tue May 6 19:45:12 2014 New Revision: 44779 URL: http://svnweb.freebsd.org/changeset/doc/44779 Log: Editorial review of intro to Terminals. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Tue May 6 18:41:56 2014 (r44778) +++ head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Tue May 6 19:45:12 2014 (r44779) @@ -619,18 +619,20 @@ - - - --> - Terminals + terminals @@ -653,8 +655,8 @@ Many terminals can be attached to a &os; system. An older spare computer can be used as a terminal wired into a more powerful computer running &os;. This can turn what might - otherwise be a single-user computer into a powerful multiple - user system. + otherwise be a single-user computer into a powerful + multiple-user system. &os; supports three types of terminals: @@ -666,9 +668,8 @@ to computers over serial lines. They are called dumb because they have only enough computational power to display, send, and receive text. - No programs can be run on these devices. Dumb terminals - connect to a computer that has all the power to run text - editors, compilers, email, games, and so forth. + No programs can be run on these devices. Instead, dumb terminals + connect to a computer that runs the needed programs. There are hundreds of kinds of dumb terminals made by many manufacturers, and just about any kind will work @@ -685,11 +686,11 @@ Computers Acting as Terminals - If a dumb terminal has just enough ability to + Since a dumb terminal has just enough ability to display, send, and receive text, any spare computer can be a dumb terminal. All that is needed is the proper - cable and some terminal - emulation software to run on the + cable and some terminal + emulation software to run on the computer. This configuration can be useful. For example, if one @@ -702,29 +703,24 @@ &os; that can be used to work through a serial connection: &man.cu.1; and &man.tip.1;. - To connect from a client system that runs &os; to the - serial connection of another system, use: + For example, to connect from a client system that runs &os; to the + serial connection of another system: &prompt.root; cu -l serial-port-device - Where serial-port-device is the name of - a special device file denoting a serial port on the - system. These device files are called - /dev/cuauN. - - The N-part of a device name is the - serial port number. - - - Note that device numbers in &os; start from zero and - not one. This means that COM1 + Replace serial-port-device with the device name of + the connected serial port. These device files are called + /dev/cuauN + on &os; versions 8.x and lower and + /dev/cuadN + on &os; versions 9.x and higher. In either case, + N is the + serial port number, starting from zero. + This means that COM1 is /dev/cuau0 in &os;. - - - Some people prefer to use other programs available + Additional programs are available through the Ports Collection, such as comms/minicom. - @@ -735,9 +731,9 @@ terminal available. Instead of connecting to a serial port, they usually connect to a network like Ethernet. Instead of being relegated to text-only applications, they - can display any X application. + can display any &xorg; application. - This chapter does not cover the + This chapter does not cover the setup, configuration, or use of X terminals.