From owner-freebsd-hackers Sun May 14 12:33:16 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA24162 for hackers-outgoing; Sun, 14 May 1995 12:33:16 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA24154 for ; Sun, 14 May 1995 12:33:15 -0700 Message-Id: <199505141933.MAA24154@freefall.cdrom.com> Received: by crh.cl.msu.edu (1.38.193.4/16.2) id AA21781; Sun, 14 May 1995 15:33:11 -0400 From: Charles Henrich Subject: Re: REMOTE_HOST & REMOTE_USER To: terry@cs.weber.edu (Terry Lambert) Date: Sun, 14 May 1995 15:33:11 -0400 (EDT) Cc: henrich@crh.cl.msu.edu, freebsd-hackers@FreeBSD.org In-Reply-To: <9505122302.AA04093@cs.weber.edu> from "Terry Lambert" at May 12, 95 05:02:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 936 Sender: hackers-owner@FreeBSD.org Precedence: bulk > The feature *I'd* like if anyone was interested anyway would be the > ability to give an argument to telnetd in inetd.conf to make it run > a program other than login (and not even prompt in the first place). > > This would let all those muck/mud/bbs/whatever programmers put up a > regular program as a telnet service, yet correctly negotiate things > like line mode protocol (by having telnetd do it on their behalf). The problem is all those programs have a single process handling all communications, so the model wouldnt map to multiple telnetd's, unless there was some well to telnetd to open a pipe back to a socket or somesuch. Good idea though, you'd think those mud/bbs folks would just pilfer the telnetd code and use it as their frontend as well. Guess that makes too much sense :) -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/