| 1 |
On Fri, May 6, 2016 at 9:40 AM, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 2 |
> On 2016-05-06, Mike Gilbert <floppym@g.o> wrote: |
| 3 |
>> On Fri, May 6, 2016 at 5:04 AM, Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 4 |
>>> On Thursday 05 May 2016 19:45:53 Mike Gilbert wrote: |
| 5 |
>>>> On Thu, May 5, 2016 at 6:03 PM, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 6 |
> [...] |
| 7 |
>>>>> Since grub-2.02 is being installed in a new slot, one would assume it |
| 8 |
>>>>> won't interfere with continue use of grub-0.97... |
| 9 |
> [...] |
| 10 |
>>>> It will not interfere with grub legacy (0.97). |
| 11 |
>>> |
| 12 |
>>> Maybe not in the slot, but when it gets installed to the MBR it will |
| 13 |
>>> overwrite the 0.97 boot code there. |
| 14 |
>> |
| 15 |
>> grub only gets installed in the MBR when you invoke grub-install or |
| 16 |
>> grub2-install. |
| 17 |
>> |
| 18 |
>> I assumed that Grant is intelligent not to run grub2-install on his |
| 19 |
>> system. |
| 20 |
> |
| 21 |
> Yes, I know not to run grub2-install (and I trust that winusb will not |
| 22 |
> do so either). Just to be sure, I'll not run winusb as root... |
| 23 |
|
| 24 |
It is entirely possible that winusb might call grub2-install with your |
| 25 |
USB disk as a target. That would also be fairly safe. |
Archives