ftp.nice.ch/pub/next/developer/resources/libraries/LGDCommunicationKit.1.0.N.a.tar.gz#/LGDCommunicationKit-1.0/Examples/connect

Makefile
 
Makefile.postamble
 
Makefile.preamble
 
PB.gdbinit
 
PB.project
 
README.rtf
[View README.rtf] 
connect.h
[View connect.h] 
connect.m
[View connect.m] 

README.rtf

README.rtf
LGDCommunicationKit, Release 1.0 (prerelease)
Examples/connect

Copyright © 1993, Looking Glass Design, Inc.
All rights reserved.

Project Manager:	Paul Girone
Original Author: 	Mike Gobbi
Creation Date:	June 26, 1993
$Revision: 1.3 $

The connect program uses the LGDSerialPort object form a simple connection to the modem, which remains active until you press control-C.

Execution

To execute this program (after making) enter
	% connect
or
	% connect device
where device is the name of the serial device to use to connect to the modem.  This should be one of cufa, cufb, cua, or cub, and there should be a hayes-compatible modem connected to the serial port corresponding to the device (A or B, depending on the last letter of the device name).

You are now connected to the modem and everything that you type will be sent unchanged (RAW mode), with the exception of the control-C character.  When this character is entered, the program will disconnect from the modem.

A comment about permissions

If the program reports a connection failure, it is likely that you do not have permission to open the devices.  If this is the case, ask your system administrator to do one of the following:
1.	Set the permissions of the devices to o+w.  This creates a potential security hole, but it provides the most protection against accidentally damaging or altering the system.
2.	Modify the executable to be setuid uucp.  This is an attractive option, since it is likely that any applications written which use the LGDSerialPort object will be running as uucp anyway.  On the other hand, if you create custom programs that run as uucp you take the risk of accidentally damaging files used by uucp.
3.	Change the ownerships of the devices to your username.  This is strongly discouraged, since it will probably cause many unix programs to fail when they are executed.
4.	Execute the self-test as root.  This is strongly discouraged.
We recommend that the first of the four options be used.  For a more detailed discussion of permissions see LGDSerialPort.rtf.

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.