From owner-freebsd-hackers@FreeBSD.ORG  Wed Feb 23 09:46:49 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C25A616A4CE
	for <freebsd-hackers@freebsd.org>;
	Wed, 23 Feb 2005 09:46:49 +0000 (GMT)
Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D540543D3F
	for <freebsd-hackers@freebsd.org>;
	Wed, 23 Feb 2005 09:46:48 +0000 (GMT)	(envelope-from marcov@stack.nl)
Received: from turtle.stack.nl (turtle.stack.nl
	[IPv6:2001:610:1108:5010::132])
	by mailhost.stack.nl (Postfix) with ESMTP id E36251F039
	for <freebsd-hackers@freebsd.org>;
	Wed, 23 Feb 2005 10:46:47 +0100 (CET)
Received: by turtle.stack.nl (Postfix, from userid 816)
	id D6CC01D9F4; Wed, 23 Feb 2005 10:46:47 +0100 (CET)
To: freebsd-hackers@freebsd.org
Date: Wed, 23 Feb 2005 10:46:47 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL118 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20050223094647.D6CC01D9F4@turtle.stack.nl>
From: marcov@stack.nl (Marco van de Voort)
Subject: ARG_MAX increase
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2005 09:46:49 -0000


I saw ARG_MAX was increased in 6.0. Recently I noticed that the
lang/fpc-devel port currently hits the old limit in certain (though rare)
cases), and this is annoying.

(some testing revealed that half the increase of 6.0 to 131k params is also
ok)

Any chance ARG_MAX will be upped in -STABLE too?