From owner-freebsd-current  Sun Aug  3 17:07:37 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA28413
          for current-outgoing; Sun, 3 Aug 1997 17:07:37 -0700 (PDT)
Received: from helbig.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28399
          for <FreeBSD-current@FreeBSD.org>; Sun, 3 Aug 1997 17:07:33 -0700 (PDT)
Received: (from helbig@localhost)
	by helbig.informatik.ba-stuttgart.de (8.8.6/8.8.5) id CAA01890
	for FreeBSD-current@FreeBSD.org; Mon, 4 Aug 1997 02:07:29 +0200 (MET DST)
From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De>
Message-Id: <199708040007.CAA01890@helbig.informatik.ba-stuttgart.de>
Subject: FD_SETSIZE in 2.2 and -current
To: FreeBSD-current@FreeBSD.org
Date: Mon, 4 Aug 1997 02:07:29 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Back in the good old days when I was playing with -current *and*
the ports collection, I've found out that FD_SETSIZE's value
differs in 2.2 (256) and -current (1024) .

As this caused some confusion during debugging the xview-lib port and 
gratutious differences between 2.2 and -current should be
avoided, I suggest to update the value of FD_SETSIZE to 1024 in 2.2 .
This is tested with the xview-lib at least and worked fine.

The man page for select(2) mentiones this value and thus needs an
update as well (see also PR bin/4177)

Wolfgang