1 |
On Thu, Aug 27, 2015 at 7:05 PM, Jeremi Piotrowski |
2 |
<jeremi.piotrowski@×××××.com> wrote: |
3 |
> On Thu, 27 Aug 2015, Neil Bothwick wrote: |
4 |
>> On Thu, 27 Aug 2015 14:19:29 +0000 (UTC), Grant Edwards wrote: |
5 |
|
6 |
|
7 |
>>> For those of us with multiple Linux installations on a disk, that's a |
8 |
>>> pretty big reason to stick with grub-legacy. |
9 |
>> |
10 |
>> Actually, that's a good scenario for GRUB2. grub2-mkconfig can detect |
11 |
>> all Linux installations on a system, not just the running one, so you |
12 |
>> only need one GRUB to boot everything. That's why distro installers are |
13 |
>> so much better at setting up Linux dual booting these days, because GRUB2 |
14 |
>> makes it simple for them. |
15 |
> |
16 |
> It's true that grub2-mkconfig does Linux detection well but the problem |
17 |
> with one grub and multiple distros is the need to manually regenerate the |
18 |
> config. |
19 |
> |
20 |
> I give you the following scenario: |
21 |
> Gentoo + another binary distro (say Fedora). Whichever one manages the |
22 |
> grub config can regenerate it on updates. On gentoo you'd do that manually |
23 |
> (post-install hooks?), Fedora would run grub2-mkconfig on kernel updates. |
24 |
|
25 |
Fedora and RHEL don't use grub2-mkconfig (unfortunately). |
26 |
|
27 |
|
28 |
> But what happens when the other one (not responsible for the config) |
29 |
> updates in a way that affects booting...? |
30 |
|
31 |
You're screwed no matter which bootloader you're using, |
32 |
|
33 |
With EFI, depending on your setup, you can update your boot entries |
34 |
without having to, for example, mount another distro's "/" or "/boot". |