From owner-freebsd-smp  Wed Jul 16 16:31:08 1997
Return-Path: <owner-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA17322
          for smp-outgoing; Wed, 16 Jul 1997 16:31:08 -0700 (PDT)
Received: from cs.utah.edu (cs.utah.edu [128.110.4.21])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA17317
          for <smp@FreeBSD.ORG>; Wed, 16 Jul 1997 16:31:06 -0700 (PDT)
Received: from fast.cs.utah.edu by cs.utah.edu (8.8.4/utah-2.21-cs)
	id RAA25188; Wed, 16 Jul 1997 17:29:36 -0600 (MDT)
Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf)
	id RAA25871; Wed, 16 Jul 1997 17:29:35 -0600
Date: Wed, 16 Jul 1997 17:29:35 -0600
From: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
Message-Id: <199707162329.RAA25871@fast.cs.utah.edu>
To: smp@csn.net, toor@dyson.iquest.net
Subject: Re: self modifying kernel code
Cc: smp@FreeBSD.ORG, terry@lambert.org
Sender: owner-smp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> There never was that much of the 486/SMP stuff anyway, relatively so.  Let's move
> and look forward, without breaking things much for existing user base.  We currently
> have NO 486/SMP user base, and IMO, our efforts are best placed on things moving
> us into the future, not the 1980s :-).
> 
> John

Hey, we have a dual 486 VTECH box that I would love to run SMP freebsd on...
It used to run NT fine on dual CPUs, but is not running uniprocessor Linux.

But you are right, it is obsolete hardware.