| 1 |
On Sat, 31 Jan 2015 15:40:37 -0700, Joseph wrote: |
| 2 |
|
| 3 |
> Indeed grub was updated to grub-0.97-r14 |
| 4 |
> |
| 5 |
> genlop --list --date 3 days ago |grep grub |
| 6 |
> Fri Jan 30 23:37:03 2015 >>> sys-boot/grub-0.97-r14 |
| 7 |
> Sat Jan 31 00:28:04 2015 >>> sys-boot/grub-2.02_beta2-r3 |
| 8 |
> |
| 9 |
> Though all my other system were updated as well, and it didn't cause |
| 10 |
> any problem, nor did I run grub-install on any of them. So I don't |
| 11 |
> think emerging/updating grub package would cause any problem unless one |
| 12 |
> run "grub-install" |
| 13 |
|
| 14 |
Well, something caused the problem. Why do you have two versions of GRUB |
| 15 |
installed? GRUB2 used t install files to /boot/grub2 but ISTR this |
| 16 |
changed recently to /boot/grub, so you could have the two packages |
| 17 |
causing some kind of conflict. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Neil Bothwick |
| 22 |
|
| 23 |
Things which must be shipped together as a set, aren't. |
Archives