On Wed, 1 Sep 1999, Bill Studenmund wrote:

> I thing mgetty might be better. getty works with modems, but assumes that
> the modem is just there. If you need to do AT command setups on the modem,
> getty won't do.

mgetty doesn't seem to be any happier.  There seems to be some basic
problem with talking to the port.  The port's okay, though; it works with
MacOS.  And NetBSD can talk with the modem port (as that's how I've got
the console hooked up).

> Do you have read/write access on /dev/tty01? where's the "permission
> denied" comming from?

I've got a couple other guys who know more than I do (Jon Lennox and Bill
Paul) looking at it, too.  They had me try:

ktrace cu -l /dev/tty01 -s 9600

...after turning off the getty on the port.  kdump produced this:

5178 cu       CALL  open(0x186f008,0x6,0xb)
5178 cu       NAMI  "/dev/tty01"
5178 cu       RET   open -1 errno 13 Permission denied

I do have read/write permission (I'm running it as root, I assume I should
be able to read/write anything I want).

> cu has always given me problems. Try tip instead.

I added the following to /etc/remote (not quite sure I understand this
part yet):

     tty01|direct connection to printer port:\
           :dv=/dev/tty01:dc:

and then I did:

     tip tty01

...and got:

     /dev/tty01: Permission denied
     link down

Does this inspire any more ideas?

-Bill

-- 
 William R. Dickson -- Consuming the Earth's limited resources since 1968
 wrd@awenet.com   < >   http://www.awenet.com/~wrd/   < >   ICQ: 14117523

		You're lucky to even know me
		You're lucky to be alive
		You're lucky to be drinking here for free
		'Cuz I'm a sucker for your lucky, pretty eyes

						-Liz Phair