Problems Building Kernel 2.4.9

Peter Barker pbarker at barker.dropbear.id.au
Wed Oct 3 23:32:11 EST 2001


On Wed, 3 Oct 2001, Donovan J. Edye wrote:

> I have the kernel source directly in /usr/src/linux (No symbolic link I

Looks OK.

my usual build process, BTW, looks something like this:
make menuconfig
make dep clean bzImage modules
su - root    #  you don't need to be root to make the kernel; I compile in
my home directory
make modules_install
cp arch/i386/boot/bzImage /boot/bzImage249
emacs /etc/lilo.conf
# add the appropriate entry to lilo.conf, either by copying an existing
# one, or more likely updating an old one.

> 1 root     root           13 Oct  4 05:15 vmlinuz -> vmlinuz-2.4.9

All this playing around with symlinks doesn't really gain you
anything. Adding multiple entries to lilo.conf gives you more flexibility
- so, for example, you can keep an old, working, copy of 2.4.9 around so
next time linus breaks things you can go back.

> * rwxr-xr-x    1 root     root       985303 Oct  3 04:41 vmlinuz-2.2.18pre21
> * rw-r-r--    1 root     root       700723 Oct  4 05:15 vmlinuz-2.4.9
> * rw-r-r--    1 root     root       700723 Oct  4 03:35 vmlinuz-2.4.9.old
> lrwxrwxrwx    1 root     root           17 Oct  4 05:15 vmlinuz.old ->
> vmlinuz-2 .4.9.old

Are those spaces really there? If so, that could be a problem!

> Looking in / I see
> * rw-r-r--    1 root     root       700723 Oct  4 05:16 vmlinuz

Usually the kernels are thrown in /boot. That wasn't always the case, of
course.

> However the above vmlinuz was not getting updated when I build the new
> kernel. So I copied vmlinuz-2.4.9 to /vmlinuz (as you see above). I then
> re-ran lilo. A reboot now does not crash the machine with the error seen,

What was the output of lilo? This is what I see when I run lilo here:
----
Added linux2410p4
Added linux247 *
Added linux247-debian
Added linux247pre1
Added linux245
Added linux
Added linux-up
Added dos
----
(Yeah, I know, I'm behind the times again.)
The "*" indicates that's the default boot option.

Here's the top from my lilo.conf:
---
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
# message=/boot/message
linear
default=linux247

image=/boot/bzImage2410p4
        label=linux2410p4
        read-only
        root=/dev/hda3

image=/boot/bzImage247
        label=linux247
        read-only
        root=/dev/hda3
---

> but it appears that the kernel that has booted is 2.2.18pre21 which is what

"uname -a" will tell you unambiguously. I strongly suggest that you _not
break_ the 2.2.18pre21 boot. Use lilo's features :-)


> * Donovan

Yours,
-- 
Peter Barker                          |   N    _--_|\ /---- Barham, Vic 
Programmer,Sysadmin,Geek              | W + E /     /\                
pbarker at barker.dropbear.id.au         |   S   \_,--?_*<-- Canberra      
You need a bigger hammer.             |             v    [35S, 149E]   
qq%I've never heard of it or used it, apart from finding it in the Camel
 book and saying "Oh god".% -- Onceler






More information about the linux mailing list