| 1 |
On 10/03/2016 05:59 PM, William Hubbs wrote: |
| 2 |
> |
| 3 |
> - The only real problem with grub:2 has to do with pperception. Yes, |
| 4 |
> their documentation has a strong preference toward using their |
| 5 |
> configuration script (grub-mkconfig) to generate your grub.cfg, but |
| 6 |
> this is not required. |
| 7 |
> |
| 8 |
|
| 9 |
Migration is not always as smooth as the guides make it out to be. I had |
| 10 |
to repartition several servers (which meant taking them offline for half |
| 11 |
an hour) to make extra space at the beginning of the drive for grub2 to |
| 12 |
install its mp3 player and angry birds and whatever else it needs to do |
| 13 |
exactly what grub1 was already doing for years. |
| 14 |
|
| 15 |
But that's not a good enough reason to keep grub1 around. If migration |
| 16 |
fails, you can just do nothing. Uninstalling grub1 won't break anything |
| 17 |
as far as I know. And new installations should use grub2 from the start, |
| 18 |
so we can totally kill it. |
Archives