From owner-freebsd-current Sun Apr 2 11:18:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA06533 for current-outgoing; Sun, 2 Apr 1995 11:18:20 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA06527 for ; Sun, 2 Apr 1995 11:18:19 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id LAA01567; Sun, 2 Apr 1995 11:17:52 -0700 Message-Id: <199504021817.LAA01567@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: sup not working In-reply-to: Your message of "Sun, 02 Apr 1995 12:00:14 +0200." <199504021000.MAA01484@uriah.heep.sax.de> Date: Sun, 02 Apr 1995 11:17:51 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >As Justin T. Gibbs wrote: >> >> FreeBSD supports transaction TCP. Almost no other vendor does. Most >> terminal servers' SLIP protocols aren't up to snuff with the new protocol >> and choke. So, if you're sitting behind a SLIP link, you should turn off >> these features (ala sysctl) and inform your ISP that they should contact >> their terminal server vendor for patches. > >Don't pass me the conical hat (i don't have any clue what T/TCP might >be good for and how i could make use of it), but i'm sitting behind a >FreeBSD 1.1.5.1 box as my SLIP dialup point -- so i guess i don't have >to disable it, right? > It wasn't in FreeBSD until 2.0R+. >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================