Date: Wed, 13 Nov 1996 16:52:42 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: Jason Thorpe <thorpej@nas.nasa.gov> Cc: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/2003: Finger does not work with many systems Message-ID: <199611132352.QAA02308@rocky.mt.sri.com> In-Reply-To: <199611132316.PAA10135@lestat.nas.nasa.gov> References: <199611132316.PAA10135@lestat.nas.nasa.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Jason Thorpe writes: > On Wed, 13 Nov 1996 15:24:12 -0800 > "Justin T. Gibbs" <gibbs@freefall.freebsd.org> wrote: > > > Actually, FreeBSD finger is a TTCP app and is probably showing that, at least > > the version of Linux running on those machines, does not have an RFC > > compliant > > TCP stack. You can disable the use of TTCP with the -T finger option. > > Eww. Rather backwards, isn't it? Shouldn't the FreeBSD finger be > compatible by default? Seems like the T/TCP code should be _enabled_ > using -T... TTCP is *compatible*. If Linux's stack were compliant then we wouldn't be having these problems. But, we allow you to enable 'backward compatability' by using a flag. If we always preferred backward compatability we'd still be using trailers in TCP/IP. :) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611132352.QAA02308>