https://bugzilla.novell.com/show_bug.cgi?id=408724
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408724#c15
Jeff Mahoney changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeffm@novell.com
Status|ASSIGNED |NEEDINFO
Info Provider| |suse-beta@cboltz.de
--- Comment #15 from Jeff Mahoney 2008-09-22 14:08:36 MDT ---
Yeah, the problem here is definitely that the old kernel is still being booted.
The file is deleted, but it's still accessible. Or, well, it will be until the
file system sees more activity.
Grub wouldn't see the old kernel because it reads the file system.
Lilo would "see" the old kernel because it doesn't understand file systems - it
just reads lists of blocks (or similar). When a file is deleted, its directory
entry is removed and the blocks occupied by it are marked as free -- but the
all the blocks are still there, unmodified, until used for something else.
Running lilo again is really the best option here. Even if it doesn't fix the
problem, I expect the problem lies in installing the boot sector (or loader),
not in the kernel. A "compile problem" that results in the kernel misreporting
its version as an older version is very unlikely.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
