| 1 |
Mike Gilbert <floppym@g.o> writes: |
| 2 |
|
| 3 |
|
| 4 |
[...] |
| 5 |
|
| 6 |
Mick wrote: |
| 7 |
|
| 8 |
>> As has already stated you could stay put with your old version, provided you |
| 9 |
>> have no specific reason to stop using it. GRUB2 can be installed and left |
| 10 |
>> unused. I guess from a usability perspective as long as you have no need to |
| 11 |
>> employ GRUB2's new functionality/features, main difference between GRUB legacy |
| 12 |
>> and GRUB2 can be boiled down to what you need to do each time you install a |
| 13 |
>> new kernel. |
| 14 |
>> |
| 15 |
>> With GRUB legacy you edit on your own your /boot/grub/grub.conf to add the |
| 16 |
>> name and version of your newly installed kernel and initrd (if you use one of |
| 17 |
>> these). |
| 18 |
>> |
| 19 |
>> With GRUB2 you run a single command line and leave it to GRUB2's scripts to |
| 20 |
>> scan your boot and other drives, discover their contents and auto-complete |
| 21 |
>> /boot/grub/grub.cfg. |
| 22 |
|
| 23 |
Mike wrote: |
| 24 |
|
| 25 |
> Harry made no mention of GRUB Legacy in his original email. I assume |
| 26 |
> he was upgrading from grub-2.02~beta3 to grub-2.02. |
| 27 |
|
| 28 |
You are correct.. `emerge world' made some kind of upgrade/update to |
| 29 |
grub2 which I've been using a fair good while. The install process |
| 30 |
ended with some kind of heads up. I didn't keep the wording emerge |
| 31 |
used but it made me think I might aught to redo actually installing |
| 32 |
into /dev/sda and grub/grub.cfg... hence my question |
| 33 |
|
| 34 |
You mentioned the version change.. but I didn't bother to investigate |
| 35 |
what the change really was. |
| 36 |
|
| 37 |
I spent a good bit of time, about 7/8 mnths ago, fearing the switch |
| 38 |
just when I had become at least sort of competent with legacy grub |
| 39 |
after years of use, and knew squat about grub 2. Finally braved up |
| 40 |
and discovered it was really very easy to get thru. |
Archives