>
> On 2001.02.13 16:31:35 +0400 Andrej Borsenkow wrote:
> > It happened to me after update to 2.4.1-8mdk which did not update
> > /boot/System.map link, was still pointing to -> 2.4.1-4mdk. May be the
> > problem
> > here as well.
> from previous answer on the list, system.map us only a list of symbols for
> kernel loggers, so it's not a critical file for boot. Morevoer, it should
> be automatically updated at boot time. If it's not, they sould be a problem
> somewhere else (maybe in you lilo conf ?)
> The symptom you are describing are exactly the one i had when using a CPU
> optimisation level too high for my box.

Hmm ... looks like it. I saw wrong link and assumed it was the reason. I
/believe/ I run lilo after rpm -U but may be I'm just dreaming. I then booted
from another partition rerun lilo and all was well again. So, most probably
the reason missing lilo.

-andrej


Reply via email to