From owner-freebsd-current Tue Mar 16 16:56:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 93B0A14CD2 for ; Tue, 16 Mar 1999 16:56:17 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id BAA17367; Wed, 17 Mar 1999 01:55:35 +0100 (CET) (envelope-from des) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: latest -current doesn't execute BSDI-binary bladeenc References: <199903160038.TAA15366@kot.ne.mediaone.net> From: Dag-Erling Smorgrav Date: 17 Mar 1999 01:55:35 +0100 In-Reply-To: Mikhail Teterin's message of "Mon, 15 Mar 1999 19:38:30 -0500 (EST)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin writes: > Does not seem a better solution to me at all. The problem is not > that bladeenc does not run, the problem is that a BSDI executable > does not run. Which breaks a promise from > http://www.freebsd.org/features.html The bug is on the web site, not in the kernel. David Greenman committed a patch to better support large memory configurations. Unfortunately, it seems this was not possible to achieve without breaking BSDI compatibility. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message