This is Problem-dialing-out-with-serial-ports in view mode; [Up]
Date: Sun 19-Aug-1991 18:11:14 From: davis@en.ecn.purdue.edu (E Robert Davis) Subject: Problem dialing out with serial ports Okay, I've read the on-line docs and the notes on modem setup from the ftp sites, but I am still having trouble dialing out. I have kermit, and I chowned it to uucp, and gave it the permissions of its owner. I changed the /etc/ttys file (the lines with ttyda and ttydb) -- changed the "unknown off" to "dialup on", and then had root kill -HUP 1 to have init reread the ttys file. But when I try to set the line to /dev/cua or /dev/cub in kermit, I get "device busy" messages. I did a ps and noticed that getty was still using ttyda and ttydb, apparently keeping kermit from using them. Is this the problem? If so, why is getty doing this. All of this happens whether I have the modem connected or not (the cable is an 040 cable from NeXTConnection -- for my 040 NeXTstation, of course). What am I doing wrong? Thanks to anyone who can help. Robert
Date: Sun 20-Aug-1991 20:45:50 From: hwr@pilhuhn.ka.sub.org (Heiko W.Rupp) Subject: Re: Problem dialing out with serial ports In article <1991Aug19.181114.14394@en.ecn.purdue.edu>, E Robert Davis writes: > -- changed the "unknown off" to "dialup on", and then had root kill > -HUP 1 to have init reread the ttys file. But when I try to set > the line to /dev/cua or /dev/cub in kermit, I get "device busy" > messages. With settin dialup on and doing kill -HUP 1, you set up the getty on the line, which then is busy. Try chanching dialup on to off. -Heiko
Date: Sun 22-Aug-1991 21:52:30 From: doug@foxtrot (Douglas Scott) Subject: Re: Problem dialing out with serial ports In article <19a55c9e.ARN1c6c@pilhuhn.ka.sub.org> hwr@pilhuhn.ka.sub.org (Heiko W.Rupp) writes: > In article <1991Aug19.181114.14394@en.ecn.purdue.edu>, E Robert Davis writes: > [beginning deleted] > > the line to /dev/cua or /dev/cub in kermit, I get "device busy" > > messages. > With settin dialup on and doing kill -HUP 1, you set up the getty on the > line, which then is busy. Try chanching dialup on to off. Has everybody made sure to do 'chown root.wheel' and 'chmod ug+s' on their versions of kermit? This solves the device busy message as long as you choose /dev/cu[f][ab] for dial-out. Today for the first time I tried setting up dial-in and -out on our new 040 cube, using one of the NeXT-to-modem cables from NeXTConnection, and I cant get the modem to respond at all. Kermit works, and allows me to enter the connect command, but I get no response. I am hoping it is some modem configuration problem only.
Date: Sun 22-Aug-1991 09:36:07 From: root@malihh.hanse.de (Carsten Lutz) Subject: Re: Problem dialing out with serial ports hwr@pilhuhn.ka.sub.org (Heiko W.Rupp) writes: >In article <1991Aug19.181114.14394@en.ecn.purdue.edu>, E Robert Davis writes: >> -- changed the "unknown off" to "dialup on", and then had root kill >> -HUP 1 to have init reread the ttys file. But when I try to set >> the line to /dev/cua or /dev/cub in kermit, I get "device busy" >> messages. >With settin dialup on and doing kill -HUP 1, you set up the getty on the >line, which then is busy. Try chanching dialup on to off. NO ! Whwn you set a dialup-getty on a dialup-line ( ttydx devices ), the line is NOT busy. The gettys will automatically step back, if another program opens the port. dialup on is OK ! Carsten
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.