Date: Mon, 12 Jun 2000 03:09:38 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Peter Wemm <peter@netplex.com.au> Cc: Mike Smith <msmith@FreeBSD.ORG>, Luoqi Chen <luoqi@watermarkgroup.com>, current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader Message-ID: <3943D5E2.A67A111B@newsguy.com> References: <20000611174153.DDB611CD7@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote: > > > 2) Add the VMware detecting to FICL, as originally suggested. > > Why make #2 vmware specific? Why not set $emulation to native,vmware,bochs, > etc. This is applicable to any platform that may have some sort of emulator. > Putting it in an environment variable has the advantage of having it passed > through to the kernel environment too, so you might be able to use it in > /etc/rc* as well. It wouldn't change the matter of having port-specific code on loader. It is really irrelevant whether that code will be setting an environment variable or returning flag/version. Forth code executed at run-time is an extension of loader. It can call various flag-returning words and set an environment variable accordingly. The only difference is that having C code set the environment variable let us get away from using FICL, but, then, the utility of it is _only_ passing it to the kernel environment, as loader(8) without FICL can do very little based on the content of an environment variable. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "He is my minion, so he doesn't need a name." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3943D5E2.A67A111B>