When I compiled a new kernel for Omega-ZIP support (RedHat 5.1), "make
zImage" copied two files to my "/" directory: "vmlinuz" and "System.map"
and I know that vmlinuz is the famous and glorious "KERNEL" :).
My first question is:
Should I add a new line in "/etc/lilo.conf" as:
image=/vmlinuz
or copy the files to "/boot" and add:
image=/boot/vmlinuz
???????? or it doesn't matter where vmlinuz resides?
I'll go ahead. Second question:
As my original "/boot" directory is as follows:
[root@wizard ] # ls /boot
total 1302
drwxr-xr-x 2 root root 1024 Dec 10 19:34 .
drwxr-xr-x 20 root root 1024 Dec 10 18:58 ..
-rw-r--r-- 1 root root 104230 May 8 1998
System.map-2.0.34-0.6
-rw-r--r-- 1 root root 512 Nov 12 18:56 boot.0300
-rw-r--r-- 1 root root 4536 May 7 1998 boot.b
-rw-r--r-- 1 root root 300 May 7 1998 chain.b
-rw-r--r-- 1 root root 168248 Nov 12 18:56
initrd-2.0.34-0.6.img
-rw------- 1 root root 18944 Dec 10 19:34 map
-rw-r--r-- 1 root root 11773 May 8 1998
module-info-2.0.34-0.6
-rw-r--r-- 1 root root 308 May 7 1998 os2_d.b
-rw-r--r-- 1 root root 444446 May 8 1998
vmlinuz-2.0.34-0.6
and I see there two files with my original kernel's extension:
"files-2.0.34-0.6". And new System.map and vmlinuz are in "/".
Why didn't my new kernel "compile" files like: "initrd-2.0.34-0.6.img"
and "module-info-2.0.34-0.6" but did so with "System.map" (without
number and version... but it did)? And what are these file for? Does
linux "use" the oldests or it doesn't need them anymore?
Do I need to send a command to generate these new files updated which
were not compiled during making new kernel?
BTW: the new kernel was compiled without any sound support. But when it
boots, dmesg says:
cannot locate sound.
but I AM SURE that the new and old ones are alternatively loaded because
of dmesg...
Why is the new kernel looking for sound if I did't included support for
sound in my last compilation? Maybe a matter of dependencies of some
other modules compiled?
TIA and see you!
--
Jos� Albores
Buenos Aires.
Argentina.
