| 1 |
On Fri, Jun 29, 2012 at 2:08 PM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
> On Fri, Jun 29, 2012 at 12:11 PM, Mike Gilbert <floppym@g.o> wrote: |
| 3 |
>> As far as I can tell, grub:0 only half-way updates itself; there is a |
| 4 |
>> large ewarn telling the user that they must take action to install the |
| 5 |
>> new version in the MBR. This seems a bit broken to me. |
| 6 |
> |
| 7 |
> In what way. As far as I can tell I haven't gotten a grub upgrade in |
| 8 |
> the last 5-7 years. Since it is built static on amd64 (or at least it |
| 9 |
> was when I last installed it) nothing ever breaks. Maybe if I changed |
| 10 |
> my boot partition to a different filesystem it might have issues, but |
| 11 |
> grub just strikes me as one of those aint-broke-don't-fix things. |
| 12 |
> |
| 13 |
|
| 14 |
Right. I was contradicting vapier's statement that grub:0 |
| 15 |
automatically updates itself. It doesn't. |
| 16 |
|
| 17 |
It does copy all of the images to /boot so that the grub shell can be |
| 18 |
used to install an MBR image. grub:2 no longer has an interactive |
| 19 |
shell and grub2-install must be used. Therefore, copying files to |
| 20 |
/boot in the ebuild is completely pointless. |
Archives