1 |
On Friday 07 Jul 2017 11:49:11 Harry Putnam wrote: |
2 |
> Mike Gilbert <floppym@g.o> writes: |
3 |
> |
4 |
> [...] |
5 |
> |
6 |
> > If you want to use the new version to boot your system, you should |
7 |
> > re-run grub-install, which will copy the modules to /boot/grub and |
8 |
> > will install the core image to your MBR or EFI system partition. |
9 |
> |
10 |
> Thanks for the info. |
11 |
> |
12 |
> I don't know what the update was but since its easy enough to run |
13 |
> `grub-install /dev/sda' and I guess also run |
14 |
> grub-mkconfig -o /boot/grub/grub.cfg |
15 |
> |
16 |
> Anyway, I did those two things... just being on the safe side. |
17 |
|
18 |
As has already stated you could stay put with your old version, provided you |
19 |
have no specific reason to stop using it. GRUB2 can be installed and left |
20 |
unused. I guess from a usability perspective as long as you have no need to |
21 |
employ GRUB2's new functionality/features, main difference between GRUB legacy |
22 |
and GRUB2 can be boiled down to what you need to do each time you install a |
23 |
new kernel. |
24 |
|
25 |
With GRUB legacy you edit on your own your /boot/grub/grub.conf to add the |
26 |
name and version of your newly installed kernel and initrd (if you use one of |
27 |
these). |
28 |
|
29 |
With GRUB2 you run a single command line and leave it to GRUB2's scripts to |
30 |
scan your boot and other drives, discover their contents and auto-complete |
31 |
/boot/grub/grub.cfg. |
32 |
-- |
33 |
Regards, |
34 |
Mick |