src/libexec/telnetd, branch releng/8.1

Convert telnetd(8) to use posix_openpt(2).

2008-11-13T19:05:27Z

Some time ago I got some reports MPSAFE TTY broke telnetd(8). Even though it turned out to be a different problem within the TTY code, I spotted a small issue with telnetd(8). Instead of allocating PTY's using openpty(3) or posix_openpt(2), it used its own PTY allocation routine. This means that telnetd(8) still uses /dev/ptyXX-style devices. I've also increased the size of line[]. Even though 16 should be enough, we already use 13 bytes ("/dev/pts/999", including '\0'). 32 bytes gives us a little more freedom. Also enable -DSTREAMSPTY. Otherwise telnetd(8) strips the PTY's pathname to the latest slash instead of just removing "/dev/" (e.g. /dev/pts/0 -> 0, instead of pts/0). Reviewed by: rink

Fix conflicts after heimdal-1.1 import and add build infrastructure. Import

2008-05-07T13:53:12Z

all non-style changes made by heimdal to our own libgssapi.

inetd and telnetd are not included in the standard release

2006-07-31T19:15:10Z

crunched floppies, but they can be included as options in src/release/picobsd (omitted by default though.) Therefore preserve the RELEASE_CRUNCH knob in their Makefiles, but tell its real purpose in a comment.

Stop enforcing dependencies between MK_* options at Makefile level.

2006-07-31T13:29:36Z

All the dependencies are satisfied now in .

telnetd(8) doesn't really go to the crunched floppies,

2006-07-31T13:20:44Z

so its Makefile needn't test for RELEASE_CRUNCH. Suggested by: ru

Respect MK_INET6_SUPPORT.

2006-07-27T12:15:37Z

Apply style.Makefile(5).

Reimplementation of world/kernel build options. For details, see:

2006-03-17T18:54:44Z

http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)

Remove kludges intended to support src trees with partial obj trees.

2005-06-10T06:12:53Z

Discussed with: ru

NOCRYPT -> NO_CRYPT

2004-12-21T10:16:04Z

Join the 21st century: Cryptography is no longer an optional component

2004-08-06T07:27:08Z

of releases. The -DNOCRYPT build option still exists for anyone who really wants to build non-cryptographic binaries, but the "crypto" release distribution is now part of "base", and anyone installing from a release will get cryptographic binaries. Approved by: re (scottl), markm Discussed on: freebsd-current, in late April 2004