1 |
On Friday 29 June 2012 01:59:37 Mike Gilbert wrote: |
2 |
> On Fri, Jun 29, 2012 at 1:13 AM, Mike Frysinger <vapier@g.o> wrote: |
3 |
> > On Monday 25 June 2012 00:15:59 Mike Gilbert wrote: |
4 |
> >> An official release of grub-2.00 should be coming pretty soon. I would |
5 |
> >> like to keyword this for ~amd64 and ~x86 shortly after it hits the tree. |
6 |
> >> I don't do much work on base system packages, so I would like some |
7 |
> >> advice on how to make this as smooth as possible. |
8 |
> >> |
9 |
> >> My main concern is that many people probably have sys-boot/grub in |
10 |
> >> @world. If grub:2 is made visible, portage will install it, and will |
11 |
> >> remove grub-0.97 on the next depclean. This could be a little confusing, |
12 |
> >> but should not cause any immediate damage since the copy of grub-0.97 |
13 |
> >> installed in the MBR and /boot would remain intact. |
14 |
> >> |
15 |
> >> Is this worthy of a news item? Or I just blog about it? |
16 |
> >> |
17 |
> >> Anything else I need to think about here? |
18 |
> > |
19 |
> > do we have automatic migration/updating in place like with grub1 ? that |
20 |
> > was the biggest reason i didn't unleash it for automatic installing on |
21 |
> > people's systems. |
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. |
32 |
|
33 |
grub1 doesn't seem to have a problem auto-updating itself. why is grub2 any |
34 |
different ? |
35 |
-mike |