| 1 |
On Fri, Jun 29, 2012 at 1:13 AM, Mike Frysinger <vapier@g.o> wrote: |
| 2 |
> On Monday 25 June 2012 00:15:59 Mike Gilbert wrote: |
| 3 |
>> An official release of grub-2.00 should be coming pretty soon. I would |
| 4 |
>> like to keyword this for ~amd64 and ~x86 shortly after it hits the tree. |
| 5 |
>> I don't do much work on base system packages, so I would like some |
| 6 |
>> advice on how to make this as smooth as possible. |
| 7 |
>> |
| 8 |
>> My main concern is that many people probably have sys-boot/grub in |
| 9 |
>> @world. If grub:2 is made visible, portage will install it, and will |
| 10 |
>> remove grub-0.97 on the next depclean. This could be a little confusing, |
| 11 |
>> but should not cause any immediate damage since the copy of grub-0.97 |
| 12 |
>> installed in the MBR and /boot would remain intact. |
| 13 |
>> |
| 14 |
>> Is this worthy of a news item? Or I just blog about it? |
| 15 |
>> |
| 16 |
>> Anything else I need to think about here? |
| 17 |
> |
| 18 |
> do we have automatic migration/updating in place like with grub1 ? that was |
| 19 |
> the biggest reason i didn't unleash it for automatic installing on people's |
| 20 |
> systems. |
| 21 |
> -mike |
| 22 |
|
| 23 |
No, the grub2 ebuild does not automatically install the files in /boot. |
| 24 |
|
| 25 |
grub2-install performs this step, and must be run by the user. It also |
| 26 |
installs the MBR and embeds the core image in unused disk sectors. |
| 27 |
This way the MBR/core image is always kept in sync with the files in |
| 28 |
/boot/grub2. |
| 29 |
|
| 30 |
I don't really see a way to reliably call grub2-install from the |
| 31 |
ebuild, and I think this would be a bit unfriendly to the user anyway. |
Archives