On Sun Oct 04 1998 00:00, Tanguy CARRABIN wrote:
> Hi all,
> thanks to your indications, I managed to get to the point where I end
> zlilo with no error message.
> However, when I restart, nothing has changed, lilo.conf is still
> pointing to the old kernel.
Then make a new entry that points to your new one.
> I report here a line that I want to ask you about:
> initrd= /boot/initrd-2.0.32.img
> This has to do with the old kernel, but what is it ? I didn't find an
> equivalent in /boot.
less /usr/src/linux/Documentation/initrd.txt
I suspect that you no longer need this, so comment it out or delete it.
(It is used to "preload" driver modules, like scsi drivers, before the
kernel actually boots up, Some installations put it there so that they can
produce installations that work for all sorts of different hardware).
> What I found in /boot is : vmlinuz-2.0.32 (the fle that is being
> currently pointed to) as well as vmlinuz. do you think vmlinuz is the
> file created by the latest kernel (2.0.35) ? is this the one I have to
> tell lilo.conf to point to ?
I'm no longer sure what a "make zlilo" does any more, I usually do "make
zImage" and move /usr/src/linux/arch/i386/boot/zImage to
/boot/vmlinuz.<kernel.version> then edit /etc/lilo.conf by hand to point to
it.
I also do "make modules ; make modules_install" and copy
/usr/src/System.map into /boot as well. You should do the same.
I strongly suspect that "make zlilo" put your new kernel image into
/vmlinuz or /boot/vmlinuz - check the file dates.
All this is well documented in files on your hard drive (or with your
distribution).
Read the kernel HOWTO, /usr/src/linux/README, and lots of documentation in
/usr/src/linux/Documentation
Cheers
Tony
