From owner-freebsd-hackers Wed Oct 15 05:15:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA05403 for hackers-outgoing; Wed, 15 Oct 1997 05:15:21 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA05377 for ; Wed, 15 Oct 1997 05:15:12 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id FAA16686; Wed, 15 Oct 1997 05:13:21 -0700 (PDT) To: Carlo Dapor cc: hackers@FreeBSD.ORG Subject: Re: 86open and implication on FreeBSD In-reply-to: Your message of "Wed, 15 Oct 1997 10:23:44 +0200." <199710150823.KAA29036@nessie.ethz.ch> Date: Wed, 15 Oct 1997 05:13:20 -0700 Message-ID: <16682.876917600@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I read the 86open 'vision'. > To me it sounds nice, having to generate simply one binary for many x86 plat- > forms. What you've read so far is very incomplete, so I would adopt a "wait for further announcements" attitude with regard to the whole 86open thing for now. The only announcement made so far hasn't even really named all of the players, something that I was worried would result in misunderstandings and which seems, in some cases at least, to have done just that, so I really do urge everyone to just give the effort a bit more time to get itself organized. More data will be forthcoming about the goals and chosen methods of the 86open effort, but until then I urge folks not to pester those involved for more details because, in many cases, even we're not sure yet. :) Jordan