brooks@tazdevil.llnl.gov (Eugene D. Brooks III) (05/01/91)
Once upon a time, you could do a kernel configuration change and create devices for terminal lines on SUNS which differered by 128 in their device number and would get incoming dialin lines which issued a hangup to the shell when the carrier was lost, and which could also be dialed out on if no login is present. The descriptions of how this works still appear in the SUN manual pages. The SPARC systems which use the eeprom funtion to control serial line and other parameters indicated that these features should work, but I have never been able to get them to work. Has anyone out there in USENET land gotten them to work? If so, HOW! Please reply by email, I rarely read this group.
geof@aurora.com (Geoffrey H. Cooper) (06/05/91)
In article <2735@brchh104.bnr.ca> brooks@tazdevil.llnl.gov (Eugene D. Brooks III) writes: >X-Sun-Spots-Digest: Volume 10, Issue 98, message 5 >X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu > >Once upon a time, you could do a kernel configuration change and create >devices for terminal lines on SUNS which differered by 128 in their device >number and would get incoming dialin lines which issued a hangup to the >shell when the carrier was lost, and which could also be dialed out on if Sure, we do it all the time. From my script: * Set up EEROM using /usr/etc/eeprom (or rom monitor): # /etc/fasthalt .... >new ... setenv tty[ab]-ignore-cd false setenv tty[ab]-rts-dtr-off false [reboot to have this take effect] b * Create dialup devices: # mv /dev/ttya /dev/ttyd[12] # mknod /dev/cua[12] c 12 128 # chown uucp.uucp /dev/cua[12] # ls -l /dev/ttyd? /dev/cua? crw------- 1 uucp 12, 128 Aug 10 17:15 /dev/cua1 crw-r--r-- 1 uucp 12, 129 Aug 10 17:30 /dev/cua2 crw--w--w- 1 root 12, 0 Aug 10 15:55 /dev/ttyd1 crw--w--w- 1 root 12, 1 Aug 10 15:04 /dev/ttyd2 * Edit /etc/ttytab: ttyd1 "/usr/etc/getty std.19200" dialup on remote ttyd2 "/usr/etc/getty std.19200" dialup on remote * Reset tty driver: # kill -1 1 As of SunOS4.1.1, it is claimed that the software can be made to appropriately ignore the EEPROM parameters, above. I haven't tried that, but have no counter-evidence. - Geof -- geof@aurora.com / aurora!geof@decwrl.dec.com / geof%aurora.com@decwrl.dec.com