From owner-freebsd-smp Wed Jul 16 10:19:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA23809 for smp-outgoing; Wed, 16 Jul 1997 10:19:41 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA23800 for ; Wed, 16 Jul 1997 10:19:38 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id KAA14374; Wed, 16 Jul 1997 10:03:45 -0700 (PDT) To: Steve Passe cc: Stephen Roome , smp@FreeBSD.ORG Subject: Re: HEADS UP: EISA cards. In-reply-to: Your message of "Wed, 16 Jul 1997 10:52:09 MDT." <199707161652.KAA08913@Ilsa.StevesCafe.com> Date: Wed, 16 Jul 1997 10:03:43 -0700 Message-ID: <14370.869072623@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > FreeBSD has a tradition for not being "snobbish" in the area of dictating > what hardware "deserves" to be supported. I see support for some things > I wouldn't pass the trash can to put into a junk box on the other side of > the room. So I don't want to ignore this side of things. (Don't take this > paragraph too literally, I agree with the policy in general, I'm just saying > you sometimes have to draw a line. Consider this a "blowing off some > steam" rant.) While this is all true, I think that SMP falls also pretty squarely into the new feature category and, as such, could easily get away with saying that old feature or system xxx is incompatible with new feature yyy and yyy simply isn't going to support it. Now if you were talking about taking out all EISA support in the uniprocessor version, well, that'd be something different. ;) JOrdan