Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3D189A8F.491BDD32@iee.org> Date: Tue, 25 Jun 2002 17:30:07 +0100 From: Don Sharp X-Accept-Language: en MIME-Version: 1.0 To: gnuwin32 Subject: Re: still cannot telnet to cygwin 1.3.10 References: <20020612053545.GA8753@redhat.com> <3D077BB4.852EC8D4@iee.org> <9516-Thu20Jun2002150244+0100-starksb@ebi.ac.uk> <3D1209B0.A18E355B@iee.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Don Sharp wrote: ... snip ... > I set CYGWIN for inetd via the registry as > > > > \Registry > > > > Machine > > > > SOFTWARE > > > > Cygnus Solutions > > > > Cygwin > > > > Program Options > > > > G:\usr\sbin\inetd.exe = binmode tty ntsec > > It might be that this is no longer a viable approach and has to be set > via the system's CYGWIN environment variable. > It turns out that when I set "CYGWIN=binmode ntsec tty" as a system environment variable everything works OK. Shame the registry entry is no longer enough! Additionally I created a local user "root" with backup priveleges so I can use the tape drives from a Unix box. Thanks again to David Starks-Browning. Cheers Don Sharp > The execute permissions are OK according to "ls" and I had tried 1.3.10 > with freshly created passwd and group. What baffles me is that all that > is necessary to produce a working arrangement is to substitute 1.3.10 > cygwin1.dll by 1.3.9. > > Anyway, I'll make further experiments soon. > > TVM > > Don Sharp ... snip ... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/