A5 Partion type confusion while dual booting DragonFlyBSD with FreeBSD

[Seann Aswell]

Understand. Earlier in the thread Siju George asked if someone would 
dual-boot OSX and Dragonfly via MBR, suggesting that A8 might work, and 
I was just confirming that indeed, someone did try. Until, that is, I 
came to my senses and used the whole drive (and later EFI) instead.

The point was to suggest that using 6C, instead of an already assigned 
code, likely made more sense. Thanks.

On 09/12/17 19:40, Matthew Dillon wrote:
> EFI doesn't have tiny little 2-byte partition id's, fortunately.  
> Instead it has 16-byte UUIDs and of course we have our own for that.  
> In anycase, for legacy MBR, I'll use 0x6C. Will push that for master 
> tonight.
>
>
>
> On Tue, Sep 12, 2017 at 11:59 AM, Seann Aswell <seann at spa104.com 
> <mailto:seann at spa104.com>> wrote:
>
>     Bad idea to install from CD using Apple bios emulation on MBR, yes.
>
>     Have used Linux and FreeBSD on that MacBook via EFI, and decided
>     if it worked to commit to DF on that machine. Thankfully, it worked.
>
>     Sent with my thumbs
>
>     On Sep 12, 2017, at 2:43 PM, karu.pruun <karu.pruun at gmail.com
>     <mailto:karu.pruun at gmail.com>> wrote:
>
>     >> I actually attempted to multi-boot OSX and Dragonfly on a
>     MacBook Pro, for what it's worth. However, quickly realized it was
>     a bad idea and installed Dragonfly on the whole drive, booting via
>     efi.
>     >
>     >
>     > Do you mean it was a bad idea when using MBR partitioning scheme?
>     >
>     > I have a multibooting macbookpro on a GPT disk with DragonFly,
>     OSX and
>     > linux, and all boot fine via EFI (with the refind boot manager).
>     > Although I'm using DragonFly for work GPT makes it easy to keep the
>     > other OSs for testing purposes.
>     >
>     > Cheers
>     >
>     > Peeter
>     >
>     > --
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20170912/ac006316/attachment-0003.htm>