Date: Sun, 28 Dec 2014 22:03:17 -0600 (CST) From: "Valeri Galtsev" <galtsev@kicp.uchicago.edu> To: "Warren Block" <wblock@wonkity.com> Cc: freebsd-questions@freebsd.org, Valeri Galtsev <galtsev@kicp.uchicago.edu> Subject: Re: FreeBSD with Win7 and UEFI Message-ID: <4209.69.209.227.251.1419825797.squirrel@cosmo.uchicago.edu> In-Reply-To: <alpine.BSF.2.11.1412281917210.51490@wonkity.com> References: <m7hfff$hno$1@ger.gmane.org> <20141226072950.GB13694@kontrol.kode5.net> <m7p8r5$jiv$1@ger.gmane.org> <alpine.BSF.2.11.1412281227150.86113@wonkity.com> <2641.69.209.227.251.1419803774.squirrel@cosmo.uchicago.edu> <alpine.BSF.2.11.1412281917210.51490@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, December 28, 2014 8:53 pm, Warren Block wrote: > On Sun, 28 Dec 2014, Valeri Galtsev wrote: >> On Sun, December 28, 2014 1:40 pm, Warren Block wrote: >>> >>> Your boot menu suggests that Windows 7 is installed for standard BIOS >>> booting. The easiest way to deal with this is to reinstall FreeBSD for >>> standard BIOS booting also, with an MBR format. Then you can install >>> the boot0 multiboot program, but it really doesn't offer anything that >>> the BIOS boot menu does not already have. >>> >>> Please also consider running FreeBSD as a VM with one of the many >>> virtualization options. That has many advantages over multiboot >>> setups. >> >> There is a big difference: in last case you have the machine running >> Windows 7. Just out of curiosity: do _you_ have the same level of trust >> to >> Windows 7/8 system as you do to FreeBSD? If yes, why at all would you go >> into trouble running FreeBSD? Just curious (no offense to >> anyone/anything >> intended ;-) > > If Windows (or anything, really) is alternately running with FreeBSD, > there's already a trust issue. The other OS has access to FreeBSD's > disks when FreeBSD is not running. > > Either way, setting up VMs is easier and less hazardous than modifying > existing disk boot blocks and partitions. Allowing multiple operating > systems to run at the same time means that the functionality of the host > or other VMs is still available. With multiboot, only one system is > available, and that can be challenging for new users who get FreeBSD > started but don't have access to the web for researching questions > because X or a text-mode browser or even a network connection has not > been set up yet. I do agree with you as far as usage of VMs is concerned, but only when I run FreeBSD as host system, and a bunch of other systems in VMs (which I have to have and use as I support these systems run on real boxes). For the goal of running windows as host system and being able to easily build and play with open source software I really would recommend to give a try to cygwin. BTW, as far as I know cygwin (created sort of under the hood of RedHat) was the first that invented to convert on the fly Linux API calls to Windows etc. Only several years (~ 5 years) later others started doing similar thing. Parallels Desktop, Virtual Box, Vmware to name three... (vmware existed forever but was originally emulating generic CPU). All is certainly much more sophisticated, so don't take me literally, and don't take my observation (who was the first etc) for ultimate truth ;-) Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4209.69.209.227.251.1419825797.squirrel>