From owner-freebsd-emulation Thu Sep 7 18:16:25 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 860C437B422 for ; Thu, 7 Sep 2000 18:16:23 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA23739; Thu, 7 Sep 2000 21:16:11 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e881GBr30904; Thu, 7 Sep 2000 21:16:11 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 7 Sep 2000 21:16:11 -0400 (EDT) To: Marcel Moolenaar Cc: Nate Williams , Bruce Evans , freebsd-emulation@FreeBSD.ORG Subject: Re: MINSIGSTKSZ [was Re: IBM JDK fails due to lack of SA_SIGINFO support] In-Reply-To: <39B837C9.F8660137@cup.hp.com> References: <200009071533.JAA05353@nomad.yogotech.com> <200009072209.QAA06661@nomad.yogotech.com> <14776.4695.816482.749092@grasshopper.cs.duke.edu> <200009072233.QAA06837@nomad.yogotech.com> <39B837C9.F8660137@cup.hp.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14776.15770.446766.141186@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marcel Moolenaar writes: > As long as MINSIGSTKSZ is larger than what the kernel actually needs to > implement the feature, we are fine. I want to look at how large this is > for different OSes that we are "close" with to determine an acceptable > value. Surely we need 2K as a high limit for Linux compatibility, but if > another OS (say SVR4) has 1K, we need to take that into account. Also, I > don't want to drive this value too low -- we can't raise it without > breaking backward compatibility. FWIW, Tru64 (aka OSF/1)'s MINSIGSTKSZ is 4k, as is Linux/alpha's Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message