According to Jose Albores: While burning my CPU.
>
> 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" :).
No realy, you can call it "anything" you want, as long as it is the same as
defined in /etc/lilo.conf
Anyway, the reason it goes to / instead of /boot is because you have not tld
"make" to put it there (in /boot), this can be done vie the top dir Makefile
in /usr/src/linux/Makefile edit it and change;
#INSTALL_PATH=/boot
to
INSTALL_PATH=/boot
>
> 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?
This is a matter of opinion etiket or whatever, i prefer /boot as i find "/"
only for directorys and not "files", which is realy what it is for.
>
>
> 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 "/".
You have vmlinuz-2.0.34-0.6 which would have a symlink to vmlinuz
(normal redhat configuration), its just that it has not shown up here in
your example. Further System.map and Modules-info are all symlinks to the
version number files.
> 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?
The only file needed for a new kernel is
/usr/src/linux/arch/i386/boot/zImage which "make" in this case copied to /
and called it vmlinuz because you told it to via the command "make zlilo"
which BTW: will NOT boot the new kernel as it seems you have not enterd a
valid entry in /etc/lilo.conf or changed the topdir Makefile as explaned
above.
As to "why didn't my new kernel "compile" files like:" it does make
System.map which contains kernel system calls for debugging perpources
and "normaly" will not be needed by your normal everyday Fred Bloggs Linux
user.
Its located in /usr/src/linux Its up to you to copy it to /boot or wherever.
The file modules.info is a referance for addresses and as far as i recall is
not needed by any programs you will use.
> Do I need to send a command to generate these new files updated which
> were not compiled during making new kernel?
Nope. But you could move the new file if you feel the need, either copy
/usr/src/linux/System.map to /boot and call it System.map-2.0.xx (where xx
is the kernel version) delete the old symlink and create a new one;
cd /boot
rm System.map
cp /usr/src/linux/System.map /boot/System.map-2.0.xx
ln -s System.map-2.0.xx System.map
or delete the System.map symlink in /boot and create
a new symlink as follows;
ln -s /usr/src/linux/System.map /boot/System.map
If you intend to keep the kernel source in place.
> 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?
I think you will find that its "Kerneld" who is looking for the sound
module and "not" the kernel, as to it being a problem, no just ignore it.
As your experiance with linux expands by the day you will find out howto
stop those messages via /etc/conf.modules. "man conf.modules" will explain.
>
> TIA and see you!
>
> --
> Jos� Albores
> Buenos Aires.
> Argentina.
>
--
Regards Richard.
[EMAIL PROTECTED]
Merry Xmas to all, and may all your troubles be small (ones).
