Re: Last chance: unresolved symbols and depmod weirdness

[Joe Bouchard <jpb@cybertours.com>]

On Sun, Mar 19, 2000 at 10:36:35PM -0500, Jonathan Markevich wrote:
> Please tell me I'm a moron and I'm clearly not running *command x*.  Please
> tell me something...  It's getting so blowing the thing away and
> reinstalling takes less time and frustration.

Hi,

Here is my cheat sheet of steps I follow every time, and it works every
time.  I will admit that there are some subtle things about modules I
don't understand, but I get the idea it is important to have version
names match because that is how the system finds them.  For instance I
have:
/lib/modules/2.0.36
/boot/System.map-2.0.36
/boot/vmlinuz-2.0.36

It seems to me once upon a time I wasn't this verbose on my filenames
and I had a lot of error messages.  I didn't add that step 15 just for
the hell of it . . . that's my notation for "I learned it the hard way."
 
======================
How to build a kernel

1)  Install the Kernel package
2)  symlink /usr/src/linux to your kernel directory
3)  cd /usr/src/linux
4)  make mrproper
5)  make xconfig
6)  make dep
7)  make clean
8)  make boot (or make bzImage)
9)  make modules
10) cd /lib/modules; mv 2.x.xx 2.x.xx-old
11) cd /usr/src/linux; make modules_install
11) cd /boot
    mv vmlinux-2.x.xx vmlinuz-2.x.xx-stock
12) cd /usr/src/linux/arch/i386/boot
    cp zImage /boot/vmlinuz
13) emacs /etc/lilo
    stock -> /boot/vmlinuz-stock
    linux -> /boot/vmlinuz
14) /sbin/lilo -v
15) make sure the module/kernel names match
16) reboot!


-- 

Thank you,
Joe Bouchard

Powered by Debian GNU/Linux