*BSD News Article 2557


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!mcsun!Germany.EU.net!news.netmbx.de!zrz.tu-berlin.de!math.fu-berlin.de!unidui!du9ds3!veit
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: 386BSD 0.1 & Com ports
References: <sxjcb.37.711773132@skyfire.uacn.alaska.edu>
Date: 22 Jul 92 12:28:42 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung
Keywords: com tip ttys remote
Sender: @unidui.uni-duisburg.de
Message-ID: <veit.711808122@du9ds3>
Lines: 48

In <sxjcb.37.711773132@skyfire.uacn.alaska.edu> sxjcb@skyfire.uacn.alaska.edu (Jay C. Beavers) writes:

>I've been trying to use tip to talk to both a line driver or a modem on com2 
>and I've had no end of trouble.  My hardware setup worked under Dos and 
>worked using the TinyBSD boot disk and basic distribution on the hard drive, 
>but once I loaded BIN01, trouble started.

># tip com2
>lock open: No such file or directory
>all ports busy

>/etc/remote contains:
>com2:dv=/dev/com2:br#9600:

>/etc/ttys contains:
>#com02	"/usr/libexec/getty std.9600"	unknown	off	secure
>com02	none				unknown	off	secure

>(I've tried this with the first line uncommented and with a status of on)

>ls -la /var/spool/lock/* contains nothing
>cat /var/log/aculog shows blank
>/dev/com2 has rw for root which I've tried this under.

>I've read as much as I can find in Managing UUCP & Usenet by ORA which has 
>fairly extensive coverage of com ports under 4.3BSD and nothing there has 
>helped.  I've even created /usr/spool/locks just on the off chance that that 
>would help.  I could find no acucntrl or uugetty on the distribution.

>So, what am I missing, and can anyone help?

> - jcb
>______________________________________________________________________________
>                                      |
>Jay C. Beavers                        |   sxjcb@orca.alaska.edu 
>University of Alaska Computer Network |   sxjcb@alaska.bitnet
>______________________________________|_______________________________________

Did you change com02 to com2 in /etc/ttys? Just an idea, at least one that
worked for me when connecting a terminal to com2 first failed.

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"