Date: Wed, 13 Nov 1996 21:14:36 -0500 From: James Risner <risner@heathers.stdio.com> To: thorpej@nas.nasa.gov Cc: freebsd-bugs@freefall.freebsd.org Subject: depends Message-ID: <199611140214.VAA09884@heathers.stdio.com>
next in thread | raw e-mail | index | archive | help
> 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... Depends on your definition of compatiable. compatible (spell fix) If it does not work to Linux or any other OS, then they are the OS at fault. The implementation is not compliant or compatiable with the RFC. What you ask is for yet another non-compliant OS by default and a flag to be compliant. I would agree with the CURRENT method. Compliant by default with a flag to BREAK the RFC. Risner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611140214.VAA09884>