home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!caen!umeecs!dip.eecs.umich.edu!dmuntz
- From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz)
- Subject: Re: 386BSD 0.1 & Com ports
- Message-ID: <1992Jul22.031943.186@zip.eecs.umich.edu>
- Keywords: com tip ttys remote
- Sender: news@zip.eecs.umich.edu (Mr. News)
- Organization: University of Michigan EECS Dept., Ann Arbor
- References: <sxjcb.37.711773132@skyfire.uacn.alaska.edu>
- Date: Wed, 22 Jul 1992 03:19:43 GMT
- Lines: 13
-
- In article <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
- ># tip com2
- >lock open: No such file or directory
- >all ports busy
-
- chown uucp /var/spool/lock or make tip suid root.
- tip is suid uucp and wasn't able to write in the lock dir (and will have
- a similar problem writing to /var/log/aculog).
-
- -Dan
-
-