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