Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!mips!mips!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!bionet!raven.alaska.edu!skyfire.uacn.alaska.edu!sxjcb
From: sxjcb@skyfire.uacn.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 & Com ports
Summary: Tip always complains of locked com port
Keywords: com tip ttys remote
Message-ID: <sxjcb.37.711773132@skyfire.uacn.alaska.edu>
Date: 22 Jul 92 02:45:32 GMT
Sender: news@raven.alaska.edu (USENET News System)
Organization: University of Alaska Computer Network
Lines: 35
Nntp-Posting-Host: skyfire.uacn.alaska.edu
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
______________________________________|_______________________________________