Dean Ridgway wrote:
>
> Greetings,
>
> I am trying to install a new Kernel and am having a little difficulty.
>
> I have followed the directions in the HOWTO and can compile the new Kernel
> (which boots), but when I do
>
> make modules
> make modules_install
>
> all I get is a single module /lib/modules/2.2.16/net/dummy.o
I won't claim that this is the cause, but I always compile my
modules while still running the old kernel. I have a script
called "makeupdate" that I install in /usr/src/linux:
make xconfig \
&& if [ .config -nt .depend ]; then
make dep && make clean
fi \
&& make bzImage \
&& make modules && make modules_install \
&& echo "From /boot run ./KernelNew."
That last message reminds me to run another script that actually
installs the kernel and updates lilo.
linuxrev=$(cd /usr/src/linux; /bin/pwd | sed -e "s%/usr/src/linux-%%")
cp /usr/src/linux/arch/i386/boot/bzImage /boot/New-vmlinuz
cp /usr/src/linux/System.map /boot/New-System.map
rm /boot/New-initrd.img
mkinitrd /boot/New-initrd.img ${linuxrev}
/sbin/lilo
And then after a few weeks when I am convinced that the new
kernel is "the one", I run KernelShift:
for file in System.map vmlinuz initrd.img; do
cp Current-${file} Old-${file}
cp New-${file} Current-${file}
done
/sbin/lilo
I hope this is useful. I've been thinking of writing it up
as a web page and/or giving a talk on it.
--
Allen Brown
work: Agilent Technologies non-work: http://www.peak.org/~abrown/
[EMAIL PROTECTED] [EMAIL PROTECTED]
I went to a strip mall the other day. Let me tell you, I was
disappointed. Everybody else had on clothes.
