From owner-freebsd-bugs  Wed Apr 10 22:47:27 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA08882
          for bugs-outgoing; Wed, 10 Apr 1996 22:47:27 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA08877
          Wed, 10 Apr 1996 22:47:23 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA29754; Thu, 11 Apr 1996 15:42:11 +1000
Date: Thu, 11 Apr 1996 15:42:11 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199604110542.PAA29754@godzilla.zeta.org.au>
To: bde@zeta.org.au, scrappy@ki.net
Subject: Re: kern/528
Cc: freebsd-bugs@freefall.freebsd.org, hsu@clinet.fi,
        scrappy@freefall.freebsd.org
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>	I guess that putting a TTYHOG/PTYHOG in sys/tty.h wouldn't be
>acceptable to circumvent this problem?  I don't assume that pty's
>generate the error that it is we are trying to fix, so seperating the
^don't
>*HOG defines would make sense, no?

The limit should be in the tty struct (and vary with the line speed).
tty.c doesn't know the difference between a pty and a tty, so it has
no way of selection between TTYHOG and PTYHOG.

Bruce