From owner-freebsd-hackers Sun Nov 22 19:16:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16227 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 19:16:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA16222 for ; Sun, 22 Nov 1998 19:16:25 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 14827 invoked by uid 1001); 23 Nov 1998 03:16:02 -0000 Message-ID: <19981122221602.D8814@numachi.com> Date: Sun, 22 Nov 1998 22:16:02 -0500 From: Brian Reichert To: freebsd-hackers@FreeBSD.ORG Subject: serial console vs ttyd0 vs cuaa0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wrangled an exploration of a serial console under 2.2.7-R, and noticed an anomoly: Well, the serial console did work right off, once I put '-P' in /boot.config. What I ran into was during my efforts to also run getty on ttyd0, so that I could freely make use of either the video console or the tty port with relative freedom. What I found: Without getty, if I simply hung the terminal off of the serial port, I could, as root, type: # cat > /dev/cuaa0 and I could get output _to_ the terminal. If I typed: # cat /dev/ttyd0 I would get no input _from_ the terminal, but # cat /dev/cuaa0 _would_ ?! Did I miss something? I had thought that ttyd was for incoming connections, and cuaa was for outgoing connections. For a workaround, I changed /etc/ttys to attach getty to cuaa0. But, that flies in the face on convention. _If_ I have muntant hardware (a Dasher 211 and a homespun cable), why did the serial console work to begin with? -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Current daytime number: (603)-434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message