On Nov 7, 2012, at 9:52 PM, Felix Miata wrote:
> On 2012-11-07 11:32 (GMT+0100) Chris Murphy composed:
>
>> It would be nice to leverage this instead of clobbering it with GRUB,
>> however it can't directly bootload linux. So while it could be the boot
>> manager, it would have to redirect the
On 2012-11-07 11:32 (GMT+0100) Chris Murphy composed:
Felix Miata wrote:
It only "squelches" when its installer finds MBR code that is
incompatible with the legacy PC BIOS standard, which is to say code that
results from installing any portion of Lilo or Grub in the MBR code
space.
Isn't i
I did the following twice:
Used fdisk to create an empty partition table.
With a 2002 Microsoft XP home disk I created an NTFS
parrtition and installed XP to it. I rebooted XP a few times
to confirm the XP installation.
I rsync'd mirrors1.kernel.org::fedora/development/18/x86_64/os
I then i
On Nov 7, 2012, at 2:40 AM, Felix Miata wrote:
>
> It only "squelches" when its installer finds MBR code that is incompatible
> with the legacy PC BIOS standard, which is to say code that results from
> installing any portion of Lilo or Grub in the MBR code space.
Isn't it true that grub2-ins
On 2012-11-06 13:42 (GMT-0800) Adam Williamson composed:
we don't support the 'install Fedora then install
Windows' case, and never have (no OS can, really, as Windows will always
just squelch the MBR at install time).
This misstates what Windows does, and vastly overstates the amount of damag
