Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!warrane.connect.com.au!kralizec.zeta.org.au!not-for-mail
From: bde@kralizec.zeta.org.au (Bruce Evans)
Newsgroups: comp.unix.bsd
Subject: Re: ttyxx logins
Date: 5 Jun 1994 18:13:59 +1000
Organization: Kralizec Dialup Unix Sydney - +61-2-837-1183, v.32bis v.42bis
Lines: 44
Message-ID: <2ss1g7$8qd@kralizec.zeta.org.au>
References: <940601172631117@busilink.com>
NNTP-Posting-Host: kralizec.zeta.org.au
In article <940601172631117@busilink.com>,
Michael Scantlen <michael.scantlen@busilink.com> wrote:
>I've received the FreeBSD 1.1 CDROM - fresh off the press... I've
>...
>I have the system with two known good 16550 Uart based serial ports.
>I pretested nullmodem cabling from one PC via terminal emulator to
>the serial ports of the FreeBSD machine - with the FreeBSD machine
>booted off DOS floppy & procomm to ensure that communications did
>exist. What I typed on one PC, showed up on the other. I then
Nullmodem connections are easiest to get working because carrier
should always be present.
>Next, I did the following: stty -f /dev/tty00 clocal
> stty -f /dev/tty01 clocal
You normally shoudn't need this "clocal hack".
Case 1: nullmodem cable. +clocal should be unecessary since carrier
should always be present.
Case 2: modem dialin. -clocal is required for correct operation.
Case 3: modem dialout. +clocal is required to talk to the modem.
The bidirectional ports ttyd0 and cua00 provide suitable clocal
settings by default but are not available without reconfiguring
and rebuilding the kernel.
Correct programs should set clocal for themself, but there are many
(generally those using the old tty interface instead of termios)
that don't even know that clocal exists.
>I then attempted to access FreeBSD - login!!! from the external PC
>still attached via cabling and the previous terminal emulator.
>Typing keys on the external PC resulted in no response or feedback.
>
>I checked ttys and found tty00 and tty01 off unknown and secure
>
>Is this the source of why I can't seem to login to FreeBSD via serial
>port, or is it the result of something else? Since this is my first
Yes. You just need to change "off" to "on" to start getty running on
selected ports.
--
Bruce Evans bde@kralizec.zeta.org.au