From owner-freebsd-emulation Sun Jun 18 20:56:55 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 842CD37B6CD; Sun, 18 Jun 2000 20:56:50 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e5J3uC502403; Sun, 18 Jun 2000 23:56:12 -0400 (EDT) Date: Sun, 18 Jun 2000 23:56:12 -0400 (EDT) From: Luoqi Chen Message-Id: <200006190356.e5J3uC502403@lor.watermarkgroup.com> To: cracauer@cons.org Subject: Re: VMware detection code in boot loader Cc: current@FreeBSD.ORG, dcs@newsguy.com, emulation@FreeBSD.ORG, msmith@FreeBSD.ORG Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In <200006131540.e5DFekh04320@lor.watermarkgroup.com>, Luoqi Chen wrote: > > It is not the loader's job to detect the underlying > > hardware configuration. > > I disagree. I would like to tell which machine I am booting on to > choose an appropriate kernel. > Eventually (it may take a while) we should be able to boot any i386/AT based machine with a single kernel which dynamically loads drivers for available hardware (and different locking modules for UP and SMP for that matter). > My -current harddisk (physically) moves between 3 machines with very > different requirements, not just SMP. FPU, few or much RAM, ISA stuff > on identical places etc. > > I can select the kernel manually, but after a crash or power fail I > might not be in a position to do it again. > > Martin > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer http://www.cons.org/cracauer/ > BSD User Group Hamburg, Germany http://www.bsdhh.org/ > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message