ok fgs@

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@

needed and we don't ship it anyway; millert@ ok.

be sure to remove filres before mknod'ing them again.
Also speed up some rm constructs.
Discussed with hugh@

with pf.conf.  If no proto is specified tcp is assumed.
dhartmei@ OK

interface optional. Suggested by rdump@river.com.
nat [on [!] <ifname>] from (any | [!] <addr>[/<mask>]) to (any |
[!] <addr>[/<mask>]) -> <addr> [proto (tcp | udp | icmp)]
rdr [on [!] <ifname>] from (any | [!] <addr>[/<mask>]) to (any |
[!] <addr>[/<mask>]) port <a>[:<b>] -> <addr> port <c>[:*]
[proto (tcp | udp | icmp)]

multicast_host/multicast_router settings; this is useful if one
flushes the routing table and re-initializes.
We really need a netconfig tool of sorts.

by ian@, and much input and mangling from theo.

anymore.

Kerberos related cleanup.

--
Ok'd by deraadt@