blob: 598866c4df2d19cfa8181d66d1f1c06b05a67e0f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
# $OpenBSD: remote,v 1.15 2014/03/18 22:36:29 miod Exp $
# from: @(#)remote 8.1 (Berkeley) 6/10/93
#
# remote -- remote host description database
# see tip(1), cgetcap(3), remote(5)
#
# Capabilities used in examples:
#
# br baud rate (defaults to 300)
# dc direct connect
# 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
# 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 or HPPA 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 capabilities 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:
doshost:\
:oe=^Z:tc=unixhost:
unixhost:\
:pa=none:br#9600:el=^U^C^R^O^D^S^Q:ie=%$:oe=^D:
tty00|For i386,macppc,vax:\
:dv=/dev/tty00:tc=direct:tc=unixhost:
ttya|For sparc:\
:dv=/dev/ttya:tc=direct:tc=unixhost:
|