Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 99548
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 98768
Assigned To: Gentoo Linux bug wranglers <bug-wranglers@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Eric Brown <eric.brown@dnbrown.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 99548 depends on: Show dependency tree
Bug 99548 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-07-19 09:45 0000 
I did emerge -uD world, glibc was among the packaged updated.  When I rebooted,
grub did not automatically start my bzImage.  I tried emerging grub again, that
did not work.  Then I ran grub -> root(), kernel(), setup(), rebooted, and it
worked.

I guess while updating some part of the system, grub's configuration got
overwritten.  Is this a CONFIG_PROTECT issue perhaps?

I am marking this as Major because if I didn't have direct access to the
machine, I would have been a sitting duck.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Sven Wegener 2005-07-19 09:46:59 0000 ------- 

*** This bug has been marked as a duplicate of 98768 ***
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug