[Gllug] New kernel compile probs

[gllug at codex.net]

On Tue, 4 Sep 2001, will wrote:

> > Running lilo does more than just interpret /etc/lilo.conf. I'd make sure
> > to run it, with the new kernel in place, just before you reboot. That's
> > all I can imagine your problem to be.
> 
> It looks like that has done it :-)
> 
> Thanks!  Apart from the embarrasing mishtake it was surprisingly easy (first
> kernel compile).

IIRC when lilo interprets the lilo.conf file, it has a look to see at what
disk offset the various kernel images are located at.  this info is then
written into the bootloader stuff.  this allows lilo to execute a
'program' without having to know about filesystems, it can just execute
from block xxx.  if you dont re run lilo, the data is for the locations of
the previous files, and hence they start to get executed.


not quite sure why it doesnt just continue booting the old image.  of
course the above could be somewhat more complicated than my explanation.


-- 


PGP key:  http://codex.net/pgp/pgp.asc


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug