Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!blackbush.xlink.net!rz.uni-karlsruhe.de!news.urz.uni-heidelberg.de!pallas.phazc.uni-heidelberg.de!cbb From: Christopher Blencowe <cbb@convex.phazc.uni-heidelberg.de> Newsgroups: comp.sys.mac.comm,comp.unix.bsd.bsdi.misc,comp.os.linux.networking Subject: Re: Weird NCSA Telnet vs BSDI/Linux bug Date: 29 Dec 1996 12:24:52 GMT Organization: University of Heidelberg, Germany Lines: 39 Message-ID: <5a5nuk$gjm@sun0.urz.uni-heidelberg.de> References: <59pgc9$p5u@blaze.cs.jhu.edu> <jwbaxter-2812962004040001@jwbaxter.olympus.net> NNTP-Posting-Host: pallas.phazc.uni-heidelberg.de X-Newsreader: TIN [UNIX 1.3 unoff BETA release 961004] Xref: euryale.cc.adfa.oz.au comp.sys.mac.comm:182110 comp.unix.bsd.bsdi.misc:5491 comp.os.linux.networking:63122 I do not know on BSDI, but for Linux the kernel speaks of some bugs with PC-TCP/IP network software, which you manually have to patch into the kernel. Maybe this is the cause for NCSA telnet to go wrong, too ? I had no probs with the older version (2.6) on my Linux machines. John W. Baxter <jwbaxter@olympus.net> wrote: > In article <59pgc9$p5u@blaze.cs.jhu.edu>, dshaw@cs.jhu.edu (David Shaw) wrote: > >Okay folks - here's a weird one: > > > >Using NCSA telnet 2.7b4 on a Mac, trying to telnet to any BSDI or Linux > >machine, if you type a control-c you can reliably crash the Mac. Total > >lockup, nothing to do but reboot. > > > >This only happens with BSDI or Linux machines. It won't happen with Irix, > >SunOS, or Solaris. > > > >I think I can safely assume the bug is on the Mac end of things... any > >suggestions on what to do? > I'm connected to a BSDI Unix machine all day (230 hours in December > through the 27th, MOST of that time with one or more NCSA Telnet sessions > going--sometimes just mail, news, etc), using 2.7b4. With no such > problems. I do remap the default meaning of control-C (in NCSA Telnet's > code, interrupt, set in the 'Sessions' preferences) to something out of > the way (control-]). That seemed essential, since control-C is rather > important to pass through uninterpreted. > --John > -- > The primary cause of problems is solutions. > John W. Baxter Port Ludlow, WA, USA jwbaxter@olympus.net -- Christopher Blencowe http://www.webservices.de