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