From 35bea87f0c2257c285012fbf6abf2d6b9a5e667b Mon Sep 17 00:00:00 2001 From: Giorgos Keramidas Date: Sat, 12 Aug 2006 15:27:06 +0000 Subject: [PATCH] Add a mini example about using cu(1) to connect to a serial port. Requested by: Soeren Straarup Assisted by: Daniel Gerzo --- .../books/handbook/serialcomms/chapter.sgml | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml index e11984983e..05e5a87efd 100644 --- a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml @@ -746,6 +746,42 @@ sio3: type 16550A spouse is busy working on your FreeBSD system's console, you can do some text-only work at the same time from a less powerful personal computer hooked up as a terminal to the FreeBSD system. + + There are at least two utilities in the base-system of + &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, you can use: + + &prompt.root; cu -l serial-port-device + + Where serial-port-device is the name a + special device file denoting a serial port of your system. + These device files are called + /dev/cuaaN + for &os; versions older than 6.0, and + /dev/cuadN + for 6.0 and later versions. + + The N-part of a device name is the serial + port number. + + + Note that device numbers in &os; start from zero and not + one (like they do, for instance in DOS-derived systems). + This means that what DOS-based systems + call COM1 is + usually /dev/cuad0 in &os;. + + + + Some people prefer to use other programs, available + through the Ports Collection. The Ports include quite a few + utilities which can work in ways similar to &man.cu.1; and + &man.tip.1;, + i.e. comms/minicom. +