From owner-freebsd-security Tue Aug 17 23: 0:21 1999 Delivered-To: freebsd-security@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id ECC0614A0B for ; Tue, 17 Aug 1999 23:00:19 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA19402; Wed, 18 Aug 1999 01:58:02 -0400 Date: Wed, 18 Aug 1999 01:58:02 -0400 (EDT) From: Mike Nowlin To: Brett Glass Cc: freebsd-security@FreeBSD.ORG Subject: RE: OpenBSD In-Reply-To: <4.2.0.58.19990817234258.0479b3b0@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > One snag, though: OpenBSD, like NetBSD, is cross-platform and is maintained > on quite a few CPUs and machine architectures. Would FreeBSD be willing to > go that route? I'd sure hope so... Let's face it -- even though FreeBSD is (in my opinion) the most "robust" out of the bunch, the x86 architecture isn't going to win any awards for performance.... Cheap, yes. Easy, yes. Works for the most part, yes. But it's still based off of the idea that we need to be backwards-compatible with the late 1700's. The Alpha port of FBSD is A Good Thing (I'm hoping to try it out this weekend on a couple of the Alpha machines I have available for playing with), but the high-end boxes are pretty pricey. You can find multi-processor SPARC machines being practically given away by companies who don't know what they're capable of, not to mention several other platforms. If the code bits are merged together properly (key word), maintaining a multiple-architecture source tree shouldn't be that difficult -- just make sure the machine-dependant parts all end up with the same ways of doing things... After all -- if Microsloth can do it with NT...... :) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message