Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Dec 2014 16:26:07 -0700 (MST)
From:      Dale Scott <dalescott@shaw.ca>
To:        "galtsev@kicp.uchicago.edu" <galtsev@kicp.uchicago.edu>
Cc:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: FreeBSD with Win7 and UEFI
Message-ID:  <F938A183-8BDD-4F3F-8B9D-942270D640E7@shaw.ca>
In-Reply-To: <2641.69.209.227.251.1419803774.squirrel@cosmo.uchicago.edu>
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>

next in thread | previous in thread | raw e-mail | index | archive | help

> On Dec 28, 2014, at 2:56 PM, Valeri Galtsev <galtsev@kicp.uchicago.edu> w=
rote:
>=20
>=20
>> On Sun, December 28, 2014 1:40 pm, Warren Block wrote:
>>> On Sun, 28 Dec 2014, Christian Baer wrote:
>>>=20
>>> This is a little redundant, but I really want to make this clear...
>>>=20
>>> My motherboard is a Supermicro X10SAT. When the system starts, I can
>>> press
>>> F12 which lets me choose the boot device (basicly like in the BIOS
>>> setup, but
>>> an a temporary basis). This is a *motherboard* function, this is not a
>>> boot
>>> manager from any OS. The motherboard recognises both Windows (list item=
:
>>> "Windows boot manager") and FreeBSD (list item: "EFI OS").
>>>=20
>>> I have seen no other boot manager after the installation nor did I see
>>> any
>>> chance to choose/configure/check one during the installation of FreeBSD=
.
>>> The
>>> handbook in rather silent about this subject too, which is quite a
>>> surprise
>>> to me. When I started out with Linux, everything was about being able t=
o
>>> coexist with Windows on a single machine. I switched to FreeBSD a littl=
e
>>> later. My first FreeBSD CDs were of v3.3 (that was 1999 and I am feelin=
g
>>> very
>>> old right about now). The FreeBSD boot manager of back then wasn't as
>>> pretty
>>> as the one supplied with SuSE at the time but it did the same thing.
>>>=20
>>> Is this an EFI thing or have the priorities shifted?
>>=20
>> UEFI is a whole new game, utterly different from what came before.  And
>> FreeBSD's UEFI support is new.  As far as I know, it has no provision
>> for multibooting in UEFI.  Code to do that would be welcome, it's been
>> difficult just to get the current UEFI support.
>>=20
>> 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.
>>=20
>> Please also consider running FreeBSD as a VM with one of the many
>> virtualization options.  That has many advantages over multiboot setups.
>=20
> 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 t=
o
> 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 ;-)
>=20
> Valeri

For me, it's about how FreeBSD enables building and experimenting with syst=
ems of applications in ways that wouldn't be possible on Windows (arguably =
from a pragmatic perspective, not necessarily technically).

Dale




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F938A183-8BDD-4F3F-8B9D-942270D640E7>