[BACK]Return to remote CVS log [TXT][DIR] Up to [local] / src / etc

File: [local] / src / etc / Attic / remote (download)

Revision 1.5, Sat Aug 11 00:05:53 2001 UTC (22 years, 10 months ago) by krw
Branch: MAIN
Changes since 1.4: +71 -28 lines

Fixup example files, man pages and phones parsing.

Make '/etc/remote' a working example, with some lengthy comments that
might help people trying to use it.

Remove untruths and beef up documentation for tip(1), remote(5) and
phones(5). In particular remove last reference to the 'cu' tip
interface since we use the 'cu' that comes with uucp, improve
documentation on phone numbers and flesh out documentation on
acu/modems supported. Document PHONES and REMOTE environment
variables.

Cleanup parsing of /etc/phones (so our example can be used) and ignore
lines with empty phone numbers instead of aborting the scan of the
file. This makes /etc/phones parsing consistant with ':pn:' capability
parsing. Don't try to dial empty phone numbers in either case.

ok millert@

#	from: @(#)remote	8.1 (Berkeley) 6/10/93
#
# remote -- remote host description database
# see tip(1), cgetcap(3), phones(5), remote(5)
#
# Capabilities used in examples:
#
#   at	ACU type
#   br	baud rate (defaults to 300)
#   dc	direct connect
#   du	make a call flag (dial up)
#   dv	device to use for the tty
#   el	EOL marks (default is NULL)
#   ie	input EOF marks (default is NULL)
#   oe	output EOF string (default is NULL)
#   pa	parity
#   pn	phone #, '\@' means use the phones(5) file
#   tc	include the named system description
#
# Most OpenBSD architectures use /dev/tty00, /dev/cua00, etc.
# for the 'standard' serial ports. Some architectures use
# /dev/ttya, /dev/cuaa, etc. The samples provide descriptions
# for the first serial port in each style.
#
# A few architectures such as the Alpha, HPPA, or mvme88k either
# don't provide a serial port by default or have more complex
# naming conventions.
#
# In all cases make sure you are using the appropriate device
# name for the port you wish to access.
#
# System names can be anything, the samples use the device name
# for simplicity.
#
# NOTE:
#       a) Multiple :tc=XXX: capabilities are allowed, so that
#          various general pieces can be assembled into one
#          system description.
#       b) Only the first capability with the same name is 
#          used. So capabilitites included a with :tc=XXX: can
#          be overridden by assigning them a value before 
#          including them. e.g. ":oe=^Z:" in doshost below.
#
# See cgetcap(3) for details on capability databases.
# --------------------------------------------------------------

# General definitions used in :tc=XXX: capabilities below
#
direct:\
	:dc:

dialup:\
        :du:at=hayes:pn=\@:

doshost:\
	:oe=^Z:tc=unixhost:

unixhost:\
	:pa=none:br#9600:el=^U^C^R^O^D^S^Q:ie=%$:oe=^D:

# Sample directly connected lines. Directly connected lines are
# most commonly used for serial consoles.
#
tty00|For Amiga,i386,mac68k,mvmeppc,powerpc,vax,hp300:\
	:dv=/dev/tty00:tc=direct:tc=unixhost:

ttya|For sun3,sparc,mvme68k:\
	:dv=/dev/ttya:tc=direct:tc=unixhost:

# Sample dial out lines.
#
cua00|For Amiga,i386,mac68k,mvmeppc,powerpc,vax,hp300:\
	:dv=/dev/cua00:tc=dialup:tc=unixhost:
cuaa|For sun3,sparc,mvme68k:\
	:dv=/dev/cuaa:tc=dialup:tc=unixhost: