Date: Wed, 19 Oct 2016 16:39:12 -0600 From: Warner Losh <imp@bsdimp.com> To: Rostislav Krasny <rosti.bsd@gmail.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: I'm upset about FreeBSD Message-ID: <CANCZdfquRep=ffpMc74mTw2rjeSWPHWyNRcdNfvX=vBbLB0Dsg@mail.gmail.com> In-Reply-To: <CANt7McH2LmmU3Kn2f3_m-Cu=%2BdrVMyHFB%2BXAW5O5XzLhUH-MYQ@mail.gmail.com> References: <CANt7McFNq%2BYSGc_9%2BH%2BUuTDO=df9Q29psRMVmiYR=q53DdBcRQ@mail.gmail.com> <CANt7McH2LmmU3Kn2f3_m-Cu=%2BdrVMyHFB%2BXAW5O5XzLhUH-MYQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 19, 2016 at 12:21 PM, Rostislav Krasny <rosti.bsd@gmail.com> wrote: > On Tue, Oct 18, 2016 at 21:57:29 +1100, Ian Smith <smithi@nimnet.asn.au> wrote: >> >> If FreeBSD GPT images (and Kindle readers) can trigger this, so could a >> theoretically unlimited combination of data on block 2 of USB media; >> modifying FreeBSD to fix a Windows bug should be out of the question. > > Not modifying FreeBSD and not fixing Windows bug but modifying the > FreeBSD installation media and working around the Windows bug to let > people install FreeBSD without disappointing at very beginning. Why > GPT is used in the memstick images at all? Why they can't be MBR > based? I think they can. Can't boot UEFI off of MBR disks on all BIOSes. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfquRep=ffpMc74mTw2rjeSWPHWyNRcdNfvX=vBbLB0Dsg>