lilo

Hi,

I just compiled a new kernel. Now I have
the vmlinux file in /usr/scr/linux-2.4.18/linux/arch/i386/boot/vmlinux If I copy the file to boot and edit the /etc/lilo.conf
and run a lilo -t -v it says file too big.
If I cp bzImage to /boot/ as vmlinux it issues vmlinux-2.4.18-initrd.img not found.
Could anyone explain to me how to
get the right files in the /boot directory and run lilo on it. I read the Kernel howto, but either something is missing
or I don't understand it (I favor the last alternative :-) and I don't want to make an error.

Thanks in advance Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

I would ignore this, to be honest. bzImage is usually a better bet.

The only file you usually need in /boot is the bzImage, and that can just be cp'd in:

cp arch/i386/boot/bzImage /boot/bzImage.2.4.18

(or use some sensible destination name). System.map is also occasionally useful, but not very often.

You then need to add an entry to lilo.conf. If you're not doing anything clever (like an initial ram disk), the entry usually goes:

image=/boot/bzImage.2.4.18
label=test
read-only

I've never needed to add anything more than that, once the rest of lilo.conf is set up.

The big exception is initrd. This is a disk image loaded by LILO, and is used by some recent distributions to store modules needed to access the real root filesystem. For custom built kernels, you almost never need this, as you can just compile the essential modules in. You might want to check in the lilo.conf that you're not trying to load a non-existent initrd, and, if you are, stop. Make sure you don't change the old image's initrd, though, or it won't work.

Steven Smith,
[email protected].

Two follow ups, if I may.

I can't locate the relevant initrd.
Where can I find it, just to get everything
correct.
The second is under /usr/src
is, as normally, a symbolic link to
my old kernel. Should I change this to the
new one, if this is the primary, or is this
not relevant?

Thanks Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs