Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
- Drop patch-af and patch-ag, both now included
(upstream)
- Update 1.2.2 -> 1.3.0
~~~~~~~~~~~~~~
15/1/2011 - Added reverse telnet server.
- Hopefully fixed masterpty client.
- Don't abuse POLLHUP.
- Support insertion of a short inter-character delay for tty
output to slow devices. (experimental).
- Add an 'exclusive' client property which, when connected, will
prevent input/output for all other connected clients.
Provide a way to specify an additional client which can
override this restriction.
- Add a timer option for exclusive clients. If they don't send
any data for a specified number of seconds, they lose their
exclusive status until they start sending again.
- New feature: Support for hot-pluggable tty(4) devices such as
USB-Serial adapters/modems. If 'pluggable true;' is specified
in the configuration file, then treat errors while
reading/writing the tty device as non-fatal. We will try to
re-open the device periodically as long as there are connected
clients. We will not disconnect clients in this case, but any
input from them will be discarded while the tty device is
unavailable.
- Pull in patches for DragonflyBSD, via pkgsrc.
Notable changes are:
- Added "closeidle true/false" to the tty server's config file
option list to tell the server that it should close the terminal
device when there are no clients connected to the service.
- If tits is invoked as "stdio2pty", it will allocate a pseudo-tty
device and connect its stdin/stdout to the master side. It will
fork(2) and exec(2) a program specified on the command line.
This program will have *its* stdin/stdout connected to the
slave side of the pty. One application for this is to execute
pppd(8) from inetd.conf.
- Add a "masterpty" client, which makes it possible associate
a pseudo-tty device with a service. For example, you can now
use tip(1) to connect to the slave pty, which will cause the
master side to be connected to the server.
- Adapt to NetBSD's more stringent <ctype> parameter checks.
- Gcc4 fixes, from Martin Husemann.
Ok'd by agc@
Changes from previous version:
1.0.3 -> 1.1.0
~~~~~~~~~~~~~~
13/04/2003 - Added a "raw" protocol, based on the existing telnet code.
- Added a "suppressbanner" client option, for the benefit of
the "raw" protocol.
1.1.0 -> 1.1.1
~~~~~~~~~~~~~~
1/09/2003 - Added "xonxoff true/false" to the tty server's config file
option list to permit changing software flow-control settings.
(Requested by Ben Elliston).
Changes since the previous point release:
- The telnet listener should not bomb out if it fails to init/add a client.
- Fix a buffer size problem in the telnet client. Note: This was not a
a buffer-overflow. It was simply getnameinfo(3) returning an error when
presented with a peer whose IP address resolved to a string larger than
NI_MAXSERV. Since NI_MAXSERV was the wrong constant to use anyway in this
context, replace it with NI_MAXHOST.
