Thanks for the prompt answer and the Welcome.
I had a look at eliloconfig but I didn't find what I was looking for. So I try to detail my question.
I'm using a PC with elilo and UEFI, so the system is booting from /boot/efi/EFI/Slackware/vmlinuz (which is not a link)
Yes, my /boot/vmlinuz is indeed a link to
Code:
lrwxrwxrwx 1 root root 20 Jan 11 17:37 /boot/vmlinuz -> vmlinuz-huge-3.10.17
whose size is 6436992
On the other end /boot/efi/EFI/Slackware/vmlinuz is an image and its size is 6441264: My original question was to find out what's the difference with the kernel-huge
The test I did was to
- take the Slackware kernel source code for 3.10.17,
- take the config-huge-3.10.17 and copied as .config
- enable the kernel options for UEFI via make manuconfig
- rebuild the kernel
hoping to get the same vmlinuz as the /boot/efi/EFI/Slackware/vmlinuz. I might have done it wrong, but I didn't get exactly the same kernel. It's working fine but the original one is performing slightly better than mine. That's why I'm looking for the config file that has been used to create /boot/efi/EFI/Slackware/vmlinuz just to make sure I didn't miss anything in the kernel configuration.
Basically I just set CONFIG_RELOCATABLE=y and CONFIG_EFIVAR_FS=y. All the other UEFI options were already set.
So it
looks like, and you might confirm, that the huge and general kernel configuration are not the ones used to generate the image in /boot/efi/EFI/Slackware
If I grep the macro
Code:
config-generic-3.10.17:457:# CONFIG_RELOCATABLE is not set
config-huge-3.10.17:457:# CONFIG_RELOCATABLE is not set
config-generic-3.10.17:5700:CONFIG_EFIVAR_FS=m
config-huge-3.10.17:5700:CONFIG_EFIVAR_FS=m
But if I miss something in the configuration and indeed the config-huge-3.10.17 has been used for /boot/efi/EFI/Slackware/vmlinuz, why its size differs from vmlinuz-huge-3.10.17?
Simply built with different options or version of gcc?
Sorry for the long mail but I'm trying to understand.
Thanks in advance for your reply.