From owner-freebsd-current Tue Mar 16 19: 0:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 71AE815053 for ; Tue, 16 Mar 1999 19:00:29 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id SAA01200; Tue, 16 Mar 1999 18:58:33 -0800 (PST) Message-Id: <199903170258.SAA01200@implode.root.com> To: Dag-Erling Smorgrav Cc: "Daniel O'Connor" , current@FreeBSD.ORG, Mikhail Teterin Subject: Re: latest -current doesn't execute BSDI-binary bladeenc In-reply-to: Your message of "17 Mar 1999 03:28:24 +0100." From: David Greenman Reply-To: dg@root.com Date: Tue, 16 Mar 1999 18:58:33 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Daniel O'Connor" writes: >> On 17-Mar-99 Dag-Erling Smorgrav wrote: >> > 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. >> Would it be feasable to have an option to switch between the two? > >Probably. I was just about to investigate this possibility. If the remaining userland issues are dealt with, then perhaps. It is currently necessary to rebuild certain utilities after changing this, however, so making it a simple kernel compile time option isn't sufficient. A much better solution would be for someone to spend the time to implement the needed VM frobbing of modifying, at BSDI binary exec-time, the ps_strings address constant in the binary's crt0 that is causing the problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message