Date: Mon, 19 Jun 2000 09:17:30 +0200 From: Martin Cracauer <cracauer@cons.org> To: Luoqi Chen <luoqi@watermarkgroup.com> Cc: cracauer@cons.org, current@FreeBSD.ORG, dcs@newsguy.com, emulation@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: VMware detection code in boot loader Message-ID: <20000619091730.A75581@cons.org> In-Reply-To: <200006190356.e5J3uC502403@lor.watermarkgroup.com>; from luoqi@watermarkgroup.com on Sun, Jun 18, 2000 at 11:56:12PM -0400 References: <200006190356.e5J3uC502403@lor.watermarkgroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In <200006190356.e5J3uC502403@lor.watermarkgroup.com>, Luoqi Chen wrote: > > 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). I have such a kernel for all my machines except SMP. However, I still boot different UP kernels on each machines for testing purposes: - different 'cpu I..._CPU' settings - different floating emulators - much or few RAM I don't want to detect all hardware, what I need is one way to tell each machine from each other, like a hostid. The ethernet address of the first card could be. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000619091730.A75581>