kayvan@mrspoc.Transact.COM (Kayvan Sylvan) (11/22/90)
I have the ESIX 5.3.2 D on a 386 with 4 Meg of RAM and a Fujitsu M2263E ESDI drive in it. It runs great!! I have a Telebit Trailblazer Plus modem hooked into COM1. In Devices, I have all the ``line'' references ending with ",M" and that should enforce the modem control. My Dialers entry starts with ``\M'' and ends with ``\m''. The problem: When I use cu to dial into another system, when I log out and the line is dropped, cu sits there still waiting for input. It's almost as if the modem control does not work. I have to do "~." to get back to the shell. Does anyone have any ideas? I read in this newsgroup (I think) that ESIX has a public access bulletin board. What is the number of that? Thanks in advance for your help! ---Kayvan -- | Kayvan Sylvan 879 Lewiston Drive W: (408) 978-1407 | | Sylvan Associates San Jose, CA 95136 H: (408) 978-1491 | | "If Donald Knuth had written X windows, it would be named Echhh windows." | | --- Marc De Groot |
darcy@druid.uucp (D'Arcy J.M. Cain) (11/23/90)
In article <KAYVAN.90Nov22013215@mrspoc.Transact.COM> Kayvan Sylvan writes: >I have the ESIX 5.3.2 D on a 386 with 4 Meg of RAM and a Fujitsu >M2263E ESDI drive in it. It runs great!! >I have a Telebit Trailblazer Plus modem hooked into COM1. >In Devices, I have all the ``line'' references ending with ",M" and >that should enforce the modem control. > >The problem: When I use cu to dial into another system, when I log out >and the line is dropped, cu sits there still waiting for input. It's >almost as if the modem control does not work. I have to do "~." to get >back to the shell. Check your devices. The minor number should 128 higher for lines with modem control. Here is part of my /dev directory: crw-rw-rw- 1 root root 3, 0 Nov 22 20:16 /dev/tty00 crw-rw-rw- 1 root root 3, 1 Nov 22 20:16 /dev/tty01 If i wanted modem control on say tty00 I would do something like this: mknod ttym00 c 3 128 Then use ttym00 in the various uucp files and inittab. See if that helps. NOTE: This works with ESIX 3.2 Rel B, C or D. See asy(7) for more details or for other versions of Unix. -- D'Arcy J.M. Cain (darcy@druid) | D'Arcy Cain Consulting | I support gun control. West Hill, Ontario, Canada | Let's start with the government! + 416 281 6094 |
jimmy@denwa.info.com (Jim Gottlieb) (11/29/90)
In article <1990Nov23.044733.1628@druid.uucp> darcy@druid.uucp (D'Arcy J.M. Cain) writes: >In article <KAYVAN.90Nov22013215@mrspoc.Transact.COM> Kayvan Sylvan writes: >>The problem: When I use cu to dial into another system, when I log out >>and the line is dropped, cu sits there still waiting for input. It's >>almost as if the modem control does not work. I have to do "~." to get >>back to the shell. > >Check your devices. The minor number should 128 higher for lines with >modem control. Here is part of my /dev directory: I have the same problem, but I am using the Megaport 24-port card. I set up the port for modem control, and modem control does in fact work on incoming calls as evidenced by the fact that hanging up from the remote end logs out the caller. But on outgoing calls, I must always do a ~. to get out. It's not a modem configuration problem, as unplugging the cable to the modem (thereby definitely dropping CD and DSR) still doesn't end the cu(1) session. Maybe I will try the new 2.0 drivers from Equinox and see if they resolve it.
kayvan@apple.com (Kayvan Sylvan) (11/29/90)
In article <KAYVAN.90Nov22013215@mrspoc.Transact.COM> Kayvan Sylvan writes: >I have the ESIX 5.3.2 D on a 386 with 4 Meg of RAM and a Fujitsu >M2263E ESDI drive in it. It runs great!! >I have a Telebit Trailblazer Plus modem hooked into COM1. >In Devices, I have all the ``line'' references ending with ",M" and >that should enforce the modem control. > >The problem: When I use cu to dial into another system, when I log out >and the line is dropped, cu sits there still waiting for input. It's >almost as if the modem control does not work. I have to do "~." to get >back to the shell. Okay, here's the solution (mentioned in the back of the release notes). The modem control device has a minor number that's 128 more than the corresponding one with no modem control. Here's my devices: crw-rw-rw- 1 root root 3, 0 Nov 25 16:56 /dev/tty00 crw-rw-rw- 1 root root 3, 1 Nov 25 16:56 /dev/tty01 crw--w--w- 1 uucp uucp 3,128 Nov 25 16:56 /dev/ttym00 You have to manually create /dev/ttym00 by doing: mknod /dev/ttym00 c 3 128 This creates the device entry which you will then use in your uucp Devices and your /etc/inittab file. If you don't want all of this to be wiped out the next time you reconfigure your kernel, also change /etc/conf/cf.d/inittab.base. In addition to inittab.base, I had to add the following to /etc/conf/bin/idmkenv since sometimes when I remake the kernel, idmknod seems to like to wipe out /dev/ttym00 (I'm sure there's a better solution to this one, but I haven't found it). ============================== cut here ============================== # # Make the modem control device after idmknod wipes it out. # if [ ! -r /dev/ttym00 ] then mknod /dev/ttym00 c 3 128 chmod 666 /dev/ttym00 fi ============================== cut here ============================== ---Kayvan
darcy@druid.uucp (D'Arcy J.M. Cain) (12/01/90)
In article <706@denwa.uucp> satyr!kayvan@apple.com (Kayvan Sylvan) writes: >You have to manually create /dev/ttym00 by doing: > mknod /dev/ttym00 c 3 128 >This creates the device entry which you will then use in your uucp >Devices and your /etc/inittab file. > >If you don't want all of this to be wiped out the next time you >reconfigure your kernel, also change /etc/conf/cf.d/inittab.base. > >In addition to inittab.base, I had to add the following to >/etc/conf/bin/idmkenv since sometimes when I remake the kernel, >idmknod seems to like to wipe out /dev/ttym00 (I'm sure there's a >better solution to this one, but I haven't found it). Yes there is. Add a ttym00 entry to the file /etc/conf/node.d/asy. Here is mine: asy tty00 c 0 asy tty01 c 1 To permanently add ttym00 add the following: asy ttym00 c 128 -- D'Arcy J.M. Cain (darcy@druid) | D'Arcy Cain Consulting | I support gun control. West Hill, Ontario, Canada | Let's start with the government! + 416 281 6094 |
cpcahil@virtech.uucp (Conor P. Cahill) (12/02/90)
In article <706@denwa.uucp> satyr!kayvan@apple.com (Kayvan Sylvan) writes: >In addition to inittab.base, I had to add the following to >/etc/conf/bin/idmkenv since sometimes when I remake the kernel, >idmknod seems to like to wipe out /dev/ttym00 (I'm sure there's a >better solution to this one, but I haven't found it). The *correct* way to fix this is to add an entry to the /etc/conf/node.d/asy file. The new entry should look like the following: asy ttym00 c 128 (assuming your mknod command is correct). -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc., uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170
abc@Matrix.COM (Alan Clegg) (12/04/90)
I have never been a user of a system that dropped the connection when carrier was dropped. Is this a common thing? I have worked with MicroVAXen, Suns, AViiONs, and most recently a 386 running ESIX. While I understand the need for modem control on tty lines, it seems to me that CU might not necessarily __WANT__ to drop the line. I might even want to make another call without giving up control of the line... -abc -- Alan B. Clegg YRAC Rural Fire Department, Wake Station 29 Matrix Corporation Support your Firefighters: Raleigh, NC The life they save might be yours