From owner-freebsd-current  Tue Jun 13  8:41: 0 2000
Delivered-To: freebsd-current@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP
	id 948F937BF30; Tue, 13 Jun 2000 08:40:48 -0700 (PDT)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.10.1/8.10.1) id e5DFekh04320;
	Tue, 13 Jun 2000 11:40:47 -0400 (EDT)
Date: Tue, 13 Jun 2000 11:40:47 -0400 (EDT)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <200006131540.e5DFekh04320@lor.watermarkgroup.com>
To: dcs@newsguy.com, msmith@FreeBSD.ORG
Subject: Re: VMware detection code in boot loader
Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Given the way VMware works, I'd have nothing against making it a FICL
> words, except...
> 
> ...VMware is a port. For some reason, I dislike the idea of having
> support targetted at exclusively one specific port. Though we have
> features added specifically to deal with certain ports, they were all
> more generic features.
> 
I'm quite reluctant to add the ficl word myself. Ideally, we should not
need to know which platform we're running on, be it a dell, a gateway
or a software emulation like vmware. The problem is our inability to
have a single kernel to boot an UP and a SMP machine, once we've solved
this problem, I would remove this ficl word. I see this as a temporary
solution to a specific problem, I don't want to generalize this into
a larger issue. It is not the loader's job to detect the underlying
hardware configuration.

-lq


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message