REMOTE(5) | File Formats Manual | REMOTE(5) |
remote
— remote
host description file
The systems known by tip(1) and their attributes are stored in an ASCII file which is structured as described by capfile(5). Each line in the file provides a description for a single system. Fields are separated by a colon (“:”). Lines ending in a \ character with an immediately following newline are continued on the next line.
The first entry is the name(s) of the host system. If there is more than one name for a system, the names are separated by vertical bars. After the name of the system comes the fields of the description. A field name followed by an `=' sign indicates a string value follows. A field name followed by a `#' sign indicates a following numeric value.
Entries named “tip*” and “cu*” are used as default entries by tip(1), and the cu(1) interface to tip(1), as follows. When tip(1) is invoked with only a phone number, it looks for an entry of the form “tip300”, where 300 is the baud rate with which the connection is to be made. When the cu(1) interface is used, entries of the form “cu300” are used.
Capabilities are either strings (str), numbers (num), or boolean
flags (bool). A string capability is specified by
capability=value;
for example, “dv=/dev/harris
”. A
numeric capability is specified by
capability#value;
for example, “xa#99
”. A boolean
capability is specified by simply listing the capability.
at
br
cm
cu
dc
di
du
dv
el
NULL
. `~' escapes are only recognized by
tip(1) after one of the
characters in `el', or after a carriage-return.fs
BUFSIZ
.hd
hf
ie
NULL
.oe
NULL
. When
tip(1) is transferring a file,
this string is sent at end-of-file.pa
pn
tc
Here is a short example showing the use of the capability continuation feature:
UNIX-1200:\ :dv=/dev/cau0:el=^D^U^C^S^Q^O@:du:at=ventel:ie=#$%:oe=^D:br#1200: arpavax|ax:\ :pn=7654321%:tc=UNIX-1200
remote
host description file resides in
/etc.The remote
file format appeared in
4.2BSD.
April 5, 2012 | NetBSD 10.99 |