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