From owner-freebsd-stable Thu Dec 7 23: 8: 5 2000 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 7 23:08:00 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 1CA6337B401; Thu, 7 Dec 2000 23:08:00 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id AAA12102; Fri, 8 Dec 2000 00:07:50 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200012080707.AAA12102@freeway.dcfinc.com> Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? In-Reply-To: from Matthew Jacob at "Dec 2, 0 01:43:18 pm" To: mjacob@feral.com Date: Fri, 8 Dec 2000 00:07:49 -0700 (MST) Cc: gallatin@cs.duke.edu, ken@kdm.org, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: chad@freeway.dcfinc.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Matthew Jacob wrote: > > Agreed. Thanks for spotting this, Andrew. > > No, we should not let users read PCI registers in such a fashion that > will cauase the system to crash. Ok, I guess just because it's the holiday season, I feel like opening a can of worms. I thought the space staked out by the *BSD gang was approximately this: NetBSD - the least amount of platform-specific code possible; run on most anything OpenBSD - pro-active security, bullet-proof from attacks FreeBSD - best performing on the Intel PC platform If that's accurate (and it may not be), then how concerned should we be about the Alpha port? Isn't Alpha (and SPARC, etc) the space stake out by the NetBSD gang? I'm not trying to foster a war here. There seems to be enough of that anyway. But unless this PCI register reading thingie is an issue for i386 boxen (and I don't think it is) we shouldn't cripple functionality on the i386 for the Alpha. Has the core group ever weighed in on this? Does the BSDi merger change any of the FreeBSD focus with regard to other hardware architectures? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message